Finance Index
What is a payment provider in the AP context - what do they actually do?
Reference guide to AP payment providers networks, including payment timing, method choices, control points, reconciliation, and vendor communication.
An AP payment provider executes disbursements on your behalf: you send one approved payment instruction set and funding, and the provider handles rail selection, bank connectivity, check printing, virtual card issuance, vendor enablement, and payment support. The trade is operational relief and multi-rail reach in exchange for an intermediary in your money flow - which makes fund-flow diligence essential.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| A payment provider | An AP payment provider executes disbursements on your behalf: you send one approved payment instruction set and funding, and the provider handles rail selection, bank connectivity, check printing, virtual card issuance, vendor enablement, and payment support. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Payment impact | Two models. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| What should we ask | Ask: Are customer funds held in FBO (for-benefit-of) accounts segregated from the provider's operating funds? | Keeps vendor records and payment decisions reliable. |
| A b2b payment network | A network where suppliers register once (identity and bank details verified centrally) and receive payments from many buyers through the network - buyers gain pre-verified payees and electronic delivery; networks monetize through buyer fees, interchange, or premium supplier services. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Related terms | Own bank: maximum control and float, lowest per-item fees, but you own connectivity, enablement, errors, and multi-rail complexity. | Keeps evidence clear and reduces control risk. |
When we pay through a provider, whose money moves first?
Two models. Good-funds: the provider debits your account first and disburses only after your funds settle - vendors are paid with your money, and the provider never extends credit. Credit-model: the provider pays vendors before collecting from you. Good-funds is the standard for AP disbursement providers; whichever model applies, you need to know exactly where your money sits between debit and vendor receipt, and under whose name.
What should we ask a provider about fund flow and what happens if they fail?
Ask: Are customer funds held in FBO (for-benefit-of) accounts segregated from the provider's operating funds? At which bank? Are you a licensed money transmitter (or exempt, and on what basis)? What happens to in-flight payments if you cease operations? What are your settlement timing SLAs and error-resolution process? A provider that answers these crisply is showing you their regulatory homework; one that waves at "bank-grade security" is not.
What is a b2b payment network and how do supplier networks work?
A network where suppliers register once (identity and bank details verified centrally) and receive payments from many buyers through the network - buyers gain pre-verified payees and electronic delivery; networks monetize through buyer fees, interchange, or premium supplier services.
Paying through our own bank vs through an AP payment provider - compared?
Own bank: maximum control and float, lowest per-item fees, but you own connectivity, enablement, errors, and multi-rail complexity. Provider: one integration, managed enablement and support, multi-rail reach, but added cost, an intermediary in the flow, and dependency risk. Many companies land on a hybrid - provider for volume disbursement, bank-direct for wires and exceptions.
What happens to our money if our payment provider goes bankrupt mid-settlement?
If funds sit in properly segregated FBO accounts, they're generally insulated from the provider's creditors; if commingled, you may be an unsecured creditor. This is exactly why FBO structure, licensing, and financial diligence belong in vendor selection.
What is an fbo account and why does our payments vendor use one?
A custodial account a provider holds at a bank "for benefit of" its customers, keeping customer funds legally separate from corporate funds - the standard architecture for compliant payment intermediaries.
How do I compare AP payment execution providers?
On settlement model and fund-flow transparency, rails supported, vendor enablement capability and ownership of vendor support, error/return handling, reconciliation outputs (1-to-1 vs lump-sum), ERP integration depth, pricing honesty (including rebate assumptions), and regulatory standing.
Is our payment provider a regulated money transmitter, and why care?
Moving third-party money generally requires state money transmitter licenses or an exemption (e.g., operating as agent of the payee, or through a bank). Licensing brings examinations, bonding, and capital requirements - a meaningful proxy for whether your disbursement partner is built to hold your money.
What is a fee-free payment network for vendors, and how do free networks fund themselves?
Networks where vendors pay nothing to receive payments; economics come from the buyer side, interchange on card rails, or optional premium services like accelerated payment - "free" always has a funding source, and you should know what it is.
What SLAs should a payment provider commit to?
Defined settlement timing per rail, acknowledgment of payment instructions, error and return resolution timeframes, support response times for both you and your vendors, and credits when SLAs are missed.
Single provider for all rails vs best-of-breed per rail?
Most mid-market teams consolidate on one provider for operational simplicity and unified reconciliation, keeping bank-direct wires as the exception path; best-of-breed per rail only pays off at volumes that justify managing multiple integrations and reconciliation streams.
Stampli perspective
Stampli supports payment provider workflows by bringing provider execution into the same P2P context as invoices, vendors, payment approvals, funding accounts, and ERP sync. Direct Pay can support multiple rails through a connected payment workflow, reducing the need for AP teams to rebuild approved payment runs in separate bank or provider portals. The value is not only payment execution; it is keeping provider outcomes, payment status, remittance context, and reconciliation evidence tied to the original AP record.