Low-code payments for enterprise billers
Add pay-by-bank to your existing payment flow
Your customers pay straight from their bank account in the page they already use, Alviere carries the license and holds the bank data, your finance team gets the reconciliation in the format it already reads, and your IT team adds it in a matter of days.
RIVERBEND ENERGY UsageBillingSupport
Up to 2% lower cost per payment on card-heavy billing mixes
Days of IT effort, not quarters of implementation
Zero bank account numbers stored in your systems
100% of ACH returns managed inside the product
Simple to build, better economics, and no regulatory weight
Getting paid by bank is an addition, not a migration. Your portal, your processor, and your month-end process all stay exactly as they are. You are adding a cheaper way for customers to pay, inside the page they already use.
One addition, web and mobile
A script tag in the payment template you already have, or the native SDK inside your app. Your fonts, your colors, your layout width. Not a redirect, not a second login, not something your customer has to download.
Days of IT effortThe economics work
Every bill that moves off a card replaces a percentage with a flat fee, and the gap widens as the bill gets bigger. A check is already a flat cost, and a smaller one replaces it. Autopay enrollment sits in the same form, so more bills arrive on time and fewer need chasing.
Lower cost per bill collectedThe regulated surface is ours
For pay-by-bank payments, the bank credentials are captured and held by Alviere, and we are the licensed money transmitter and ACH originator of record. Your card flows carry on untouched, and nothing sensitive has to land in your systems.
PCI · SOC 2 · NMLS 1738907Accepting the payment, then settling funds back to you.
This applies to the bills your customers choose to pay by bank. Your card payments carry on exactly as they do today. For the ones that come through us, the sensitive part stays with us, and everything after it comes back to you: the cash, the file your team already reads, and only the exceptions that genuinely need a person.
What stays yours
What we take care of
When a bill gets paid
Your page, your brand, your customer
Customers pay where they have always paid. No redirect, no second login, no app to download, and no letter explaining that billing has changed.
The payer, their details, and the payment itself
We display all the screens under your brand, seamlessly embedded. We verify the payer, store their methods and preferences, and originate the payment. The license and the obligations are ours.
When a payment settles
The cash, and the file your team already reads
Money lands in your own account on a calendar treasury can model. Reconciliation arrives in the format you use today. Only the exceptions that need a person reach your team.
Chasing what fails, and the calls that come with it
Failed payments and retries, fraud screening, the disclosures the rules require, and the support line when a customer rings about a payment.
Autopay
Give us your billing cycle. We'll take care of the rest.
If you already have autopay capabilities, pay-by-bank becomes a payment execution you invoke. If you don't, enrollment sits in the same component as the one-time payment, offered at the moment the customer is already paying, which is the highest-converting position in the flow.
- Settings you define and the customer picks. Pay on the due date or a chosen day. Full balance or a capped amount. Per account or per policy. Pause, resume, or change the funding account without re-enrolling.
- Cycle-driven scheduling. Send us the billing file, or call the API with amount and due date. We time the debit to land on time, allowing for settlement.
- Retries that think. Failed payments are retried on a schedule tuned to the return reason and to payday patterns, within Nacha reinitiation limits. You see every attempt as it happens, and the customer is notified rather than silently re-debited.
- Notices generated for you. Pre-debit notification, change-of-amount notices and revocation handling ship inside the component, so your communications team doesn't build them.
Timely payment, every cycle
Auto-retry on failure
Higher enrollment
How it works
You hand us the billing cycle: a file or an API call carrying account, amount and due date. Alviere holds the customer's autopay preferences, times the debit against settlement, retries intelligently on returns, and issues the notices recurring debits require. Enrollment, changes and cancellations all happen inside your own interface, and every state change comes back to you as a webhook.
Returns & fraud
Returns land in the process you already run
Full ACH return management is part of the product, not a separate queue for someone on your team to own. It blends into your existing chargeback workflow and your bad-check routine, so nobody has to learn a new process.
- Machine learning fraud prevention on every enrollment and every transaction, scoring device, behavior, velocity and account history before the debit is originated.
- Bank account ownership and status validation at first use, which as of March 2026 is a Nacha requirement for consumer web debits rather than an optional control. We do it; you inherit it.
- Biller-specific abuse cover for account takeover on the payment page, and for third parties paying a bill they have no right to touch.
Fraud screened up front
Returns triaged for you
Return-rate limits are ours
How it works
Every return arrives with an R-code. Alviere classifies it, decides whether a retry is permitted and sensible, and either resolves it or hands it to you already triaged, mapped into the queue your team already works, with the SLA it already runs. You configure the routing once. Return-rate monitoring and the Nacha thresholds that go with it stay with us.
Reconciliation & finance ops
Reconciliation the way your processor already does it
The hidden cost of changing payment providers is not the integration. It is the month of controller time nobody budgeted. So we adapt to your file, not the other way around.
- Your current layout, your cadence. We map to the file your processor sends today: same fields, same delivery method, same time of day. Your close doesn't change.
- One trace ID, end to end. Carried from authorization to settlement to return, so straight-through matching works on day one.
- Webhooks into the system you actually run. Whether that is billing, AR or policy administration, events post in the shape your systems expect. Daily reconciliation files are also provided.
- A funding calendar you can model. Settlement timing and cut-offs stated plainly, because treasury forecasts cash and needs the inputs.
- Refunds and credits to the same token. Overpayments, cancellations and budget-billing true-ups go back the way they came.
Your existing file format
Straight-through matching
Real-time status webhooks
How it works
During implementation your controller sends us a sample of the reconciliation file they read today. We map our output to it and confirm it against a parallel run before go-live. From then on the file arrives on the same schedule, in the same shape, with an added trace ID. The exceptions view shows what returned, why, what is being retried and what needs a human.
We hold the license, the data and the obligations
Alviere is the licensed money transmitter of record (Mezu (NA) Inc. d/b/a Alviere, NMLS ID 1738907) and the ACH originator. Nacha rule changes, validation mandates, and originator obligations are ours to absorb.
Funds are safeguarded, not commingled
Held under state permissible-investment requirements and never mixed with Alviere's operating cash, until they settle to your account.
Sensitive data stays out of your environment
Fewer systems in PCI scope, no Nacha file handling, no stored bank credentials for an attacker to find.
The disclosures ship inside the component
Money-transmission identification, state complaint legends and Regulation E language render with the payment form, so your legal team does not build them.
Live support for the payment itself
A toll-free line staffed for transaction inquiries, refunds and error claims. You keep the billing relationship; we take the payment calls.
Billers we are built for
Utilities
Monthly cycles, disconnect rules, and returns that run against a regulatory clock.
Insurance
Premiums that have to land before a policy lapses, across lines that each bill differently.
Healthcare
Patient balances paid late, in installments, long after the visit.
Property management
Rent due on the first, across portfolios that each reconcile their own way.
Telecom
High volume, thin margins, and churn that follows a failed payment.
Municipal services
Taxes, utilities and fees collected under public procurement rules.
Three things for IT. Everything else is a finance conversation.
Your server mints the JWT, your page includes the SDK
<!-- one script, one element, in the page you already have -->
<script type="module" crossorigin="anonymous"
src="https://js.prd.alvierecdn.com/ui/latest/web-components.js"></script>
<!-- Backend mints the JWT and mounts the SDK. All logic handled inside -->
<alviere-multi-step-flow
jwt="SERVER_MINTED_JWT"
business-uuid="ALVIERE_PROVIDED_UUID"
config='{
"steps": [
{ "type": "CREATE_CONSUMER_ACCOUNT", "label": "Your details" },
{ "type": "ADD_BANK_ACCOUNT", "label": "Your account" },
{ "type": "CHECKOUT_CONFIRM", "label": "Confirm payment" }
],
"amount": 214.55,
"showProgress": true
}'
></alviere-multi-step-flow>Your server submits the confirmed payment
document
.querySelector('alviere-multi-step-flow')
.addEventListener('flow-complete', (event) => {
// event.detail.result carries all the information you need
postToYourLedger(event.detail.result);
});Note: webhooks directly to your backend are also available.
From signature to first live payment
- Week 1 Finance kick-off
Billing cycle, file formats, settlement account, returns routing rules. Your controller sends us the reconciliation file they read today.
- Week 2 Design and configuration
We map to your file, set up the autopay rules and stand up your sandbox. We define the rules and flows together, and finalize on the SDK inputs from you.
- Week 3 The IT sprint
Server-side token call, the script include, and the call that submits the confirmed payment.
- Week 4+ Testing and parallel run
Live payments alongside your existing processor, reconciliation compared line for line before anything is switched over.
- Then Turn up the volume
Promote pay-by-bank in the flow at whatever pace your CX team is comfortable with.
- No new vendor infrastructure
- No Nacha files
- No portal migration
- Your processor stays
What you need to know
-
No. It runs alongside what you have. Cards stay exactly where they are, on the same processor, under the same contract. We are changing your payment mix, not replacing your stack, which is also why this can go live in weeks rather than quarters.
-
The integration files stay the same, which is the part that normally costs the most. Alviere delivers the same file your card processor sends you today, in the same format and on the same cadence, so nothing downstream of the payment has to be rebuilt or retested. The new work is three small pieces: a server-side call that mints the JWT, a script include and one element in your existing payment template, and a server-side call that submits the confirmed payment.
-
In Alviere's environment, encrypted and maintained by us under PCI and SOC 2 controls. Your systems do not need to hold anything: we return the token on the reconciliation file, keyed to your own account reference. Storing that token on your side is optional, so it stays off your IT backlog unless you want it. Either way, if your database were exposed tomorrow there would be no bank credentials in it to expose.
-
Alviere is the originator and the licensed money transmitter of record. Origination obligations, return-rate thresholds and rule changes such as the March 2026 account-validation requirement sit with us. Your own compliance obligations as a biller don't vanish, and we won't pretend otherwise. But the money-transmission licensing and the ACH origination burden are ours.
-
The R-code is classified, retried where that is permitted and sensible, and the customer is notified. Only what genuinely needs a human reaches your team, and it arrives in the queue you already work, whether that is your bad-check routine or your card chargeback intake.
-
In the file format you read today. During implementation your controller gives us a sample of your current processor's output and we map to it: same fields, same cadence, same delivery method, plus a per-transaction trace ID that makes straight-through matching work from day one. Your month-end close does not change shape.
-
Generally yes, though fee models are state-regulated and rule-bound, so the honest answer is that it depends. Pay-by-bank costs you materially less to accept than a card, which is what gives most billers the room to reduce or remove the fee, a customer-satisfaction win that usually pays for itself in call volume. Bring us your current fee structure and we'll work through it with you.
-
Manual routing and account entry is fully supported, with no bank login required and no third-party app in the middle. Validation happens either way, so the risk profile is the same regardless of how the customer got their details to us.
-
Yes. Your brand, your page, your flow, your fonts. The required money-transmission identification, state complaint legends, Regulation E language and support number render inside the component. They are obligations you would otherwise have to build, and here they arrive with the form.
-
Your choice. Either our toll-free line handles payment questions (inquiries, refunds, error claims), or your team keeps them and we supply the transaction data behind each one. Give it to us and a category of call leaves your service desk; keep it and you remain the only voice your customer hears.
-
Four to six weeks is a realistic plan for a first cohort, including a parallel run against your existing processor before anything switches over. The timeline above shows where the effort actually falls: mostly on finance in weeks one and two, briefly on IT in week three.
-
You should ask this of any payment provider, and most won't answer it on their website. Stored payment tokens are portable and your customer and transaction data is exportable in standard formats. The specific commitments live in the agreement. Ask us for them in writing before you sign, and hold us to them.
-
The industry word for what sits in the middle of this. We hold the account number and return a token on the reconciliation file, so the sensitive part stays inside our environment. It is the same thing your card processor already does with saved cards, applied to bank accounts. Storing that token on your side is optional and comes down to how much IT work you want to take on: it is worthless to anyone who steals it, and you do not need it to reconcile.
Tell us about your billing cycle. We'll tell you what it should cost.
Bring your volume, your payment mix and the reconciliation file you read every morning. We'll come back with a modelled saving, a mapped file and an implementation plan tailored to your business.
Money-transmission services provided by Mezu (NA) Inc. d/b/a Alviere, NMLS ID 1738907.