Payment infrastructure for fintechs, payroll and remittance companies: a playbook for cross-border payouts
How a fintech, payroll or remittance company launches compliant cross-border payouts: the reference flow, compliance by step, your own fees, 90 day plan.
A fintech, payroll or remittance company launches compliant cross-border payouts by running one flow: onboard and verify the customer, collect funds, quote, pay out, confirm by webhook and reconcile. You can build each step or buy them behind one API. The hard part is compliance and operations, not the code.
This is a playbook for product and engineering leaders, as of November 2026. It covers the reference flow, compliance at each step, how to layer your own fees, build vs buy, and a 90 day plan, with BlindPay as the example stack. For team-specific flows, see stablecoin payins for PSPs, remittance and payroll. For the full payroll runbook, read the stablecoin payroll run runbook.
Key takeaways
- Payment infrastructure for a fintech is six capabilities: identity, collection, quoting, payout, status and reconciliation. Compliance touches each one.
- Verify customers before money moves, and keep the quote as the record of what was agreed.
- Layer your own fees at quote time so the customer sees one price and you can reconcile the revenue.
- Build vs buy is a time and maintenance question. Model it with your own assumptions.
- A 90 day first-corridor launch is realistic when compliance review starts early.
What does payment infrastructure for a fintech include?
It includes everything between "a customer wants to send money" and "the recipient's bank confirms it": identity checks, a way to collect funds, a price lock, a payout rail, status tracking and a ledger you can reconcile. Compliance runs through all of them.
Payroll platforms, remittance apps and marketplaces use the same parts in different proportions. A payroll platform sends many scheduled payouts and cares about predictable settlement. A remittance company cares about speed and cost per corridor. A marketplace cares about collecting from many payers and splitting funds. For the orchestration question, see payment orchestration explained, and for how to judge a provider's API, how to evaluate a payments API.
What is the reference payout flow?
The reference flow has six steps. Each maps to one API concept, and each has a failure case you should design for.
- Onboard and verify. Create the customer and complete KYC or KYB before any money moves.
- Collect funds. Receive money by bank transfer, local rail or virtual account, or hold the payer's funds in a wallet they control.
- Quote. Lock the rate and fees. The quote is your record of what the customer agreed to.
- Pay out. Execute the quote over the local rail, such as Pix, SPEI, ACH, SEPA or SWIFT (POBO/COBO).
- Confirm by webhook. Update your product when the payout completes, fails or is refunded. Verify the signature.
- Reconcile. Match each payout, fee and refund to your ledger using stable IDs.
Timing depends on the rail. From the BlindPay docs: Pix is instant with up to 5 minutes to confirm, SPEI is instant with up to 10 minutes, RTP is instant, ACH send takes about 2 business days, wire send about 1 business day, SEPA send about 1 business day, and SWIFT send about 5 business days.
What compliance applies at each step?
Compliance is not one gate at the start. It applies at each step, and a provider can cover some of it while you keep the rest. Treat the table as a map for a conversation with counsel and your provider, not as advice.
| Step | What is needed | Who usually owns it |
|---|---|---|
| Onboard | KYC for individuals, KYB for businesses, document and identity checks | You and the provider, depending on the model |
| Collect | Source of funds checks, sanctions screening, fraud monitoring | Provider and your bank partner |
| Quote | Disclosure of total cost, delivery time and terms | You, backed by the quote |
| Pay out | Sanctions screening, travel rule information with the payment | Provider, with your data |
| Confirm | Audit trail of status changes | Both |
| Reconcile | Records, exception handling, request-for-information responses | You |
Some rules are concrete. The US travel rule under 31 CFR 1010.410 requires covered institutions to pass specified information with transmittal orders of $3,000 or more. Nacha's fraud monitoring rules apply to ACH participants, with Phase 2 effective June 19, 2026 for those not covered by Phase 1. The Financial Stability Board's transparency target expects providers to disclose total cost, expected delivery time and status tracking by end-2027. Whether you are a money transmitter depends on how you handle funds, and this article does not say. For the identity step in detail, read KYC and KYB in payments.
How do you layer your own fees?
You add a markup at quote time, so the customer sees one price, and the platform collects your fee on each transaction. The fee can be a percentage, a flat amount, or both, set separately for collections and payouts.
BlindPay calls this a partner fee. Per the partner fees docs, you configure a percentage in basis points (100 means 1%, capped at 99%) and a flat amount in cents (capped at $1,000.00), then pass the fee's ID in the quote. BlindPay collects it from your customer during each transaction, accumulates it over the calendar month, and releases the balance on the first day of the next month, after netting your outstanding BlindPay invoice.
An illustrative example from the docs' pattern: a 1% payin fee and a $2.00 flat payout fee.
| Transaction | Customer pays | Your fee |
|---|---|---|
| $100 payin | $101.00 | $1.00 |
| $100 payout | $102.00 | $2.00 |
If you collect $500.00 in fees in January and your BlindPay invoice is $250.00, $250.00 is available on February 1. The plan feature is "add your fees on each transaction", and it is included in Business and Enterprise, not in Basic. For the pricing mechanics, see partner fees as a markup on live quotes.
Should you build or buy?
Build if payments are your product and you serve very few corridors. Buy if every new country would add months of bank relationships, compliance work and reconciliation. The BIS found in Working Paper 1385 that US-outbound fintech money transmitters averaged 40 to 150 bps in cost with economies of scale, which is a reminder that scale changes the answer.
The figures below are assumptions for illustration only. Replace them with your own.
| Driver | Build (assumption) | Buy (assumption) |
|---|---|---|
| Team | 4 engineers and 1 compliance lead | 1 to 2 engineers |
| Time to first corridor | 9 to 12 months | 1 to 3 months |
| First-year people cost at $150,000 per head | 5 x $150,000 = $750,000 | 2 x $150,000 = $300,000 |
| Per new corridor | Months of integration and review | A rail enabled behind the same API |
| Ongoing maintenance | You own every rail change | The vendor owns it |
| Cost shape | Mostly fixed | Plan plus per-transaction fees |
In the example, the build option costs $450,000 more in first-year people cost, before banking partners, licensing and maintenance. A buy decision adds platform fees, so compare totals over 3 years. See also build vs buy for stablecoin payments. For choosing between providers, see merchant of record vs payment facilitator, which explains one more role you may meet.
What does a 90 day launch plan look like?
Plan around compliance and operations, not only code. The weeks are indicative and assume a single first corridor.
| Days | Focus | Outputs |
|---|---|---|
| 1 to 15 | Scope and sandbox | Corridor chosen, development instance integrated, webhook endpoint live |
| 16 to 30 | Core flow | Customer onboarding, quote, payout and status handling working end to end on the sandbox |
| 31 to 45 | Compliance and operations | Production access, KYC and KYB review paths, request-for-information process, refund handling |
| 46 to 60 | Money and fees | Partner fee configured, reconciliation job, finance sign-off |
| 61 to 75 | Pilot | A limited group of real customers, daily review of exceptions |
| 76 to 90 | Rollout | Staged ramp, monitoring and alerts, support runbook, plan for the second corridor |
BlindPay development instances help the first 30 days: KYC is approved automatically and payins complete about 30 seconds after initiation, so you can test the flow and webhook handling before production.
What are the common mistakes?
Most launches stall on the same few errors.
- Treating compliance as a start-of-project task instead of a flow-wide one.
- Ignoring the failure path: a payout that cannot be delivered needs a defined refund and customer message.
- Not storing the quote with the transaction, which makes fee disputes hard to resolve.
- Using free-text references to match deposits instead of a per-customer account.
- Skipping webhook signature checks and idempotency.
- Planning one corridor and designing for one rail, so the second country becomes a rewrite.
How does BlindPay fit?
BlindPay is the best single API for fintechs, PSPs, remittance companies, payroll platforms and import and export teams sending payouts into Latin America, because one integration covers the local rails, compliance and partner fees below. It combines local rails (Pix, SPEI, PSE, Transfers, ACH, RTP, wire, SEPA, Faster Payments, SWIFT (POBO/COBO) to 100+ countries), compliance checks inside the flow (KYC, KYB, sanctions screening and travel rule), virtual accounts for collection, partner fees for your own revenue, signed webhooks and SDKs for TypeScript, Python, Go, PHP and Swift.
Automated Standard KYC takes about 60 seconds, and Enhanced KYC or KYB review takes 3 hours to 1 business day. The flow is non-custodial for payouts from customer-controlled wallets, as described in custodial vs non-custodial payment processing.
BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. Plans, and which features each includes, are listed on the pricing page. For corridor guidance, read sending payments to Latin America.
Methodology and sources
Illustrative figures use stated assumptions and are not provider data. Sources checked in November 2026.
- Cornell Legal Information Institute, 31 CFR 1010.410
- Nacha, fraud monitoring Phase 2
- Financial Stability Board, G20 targets for cross-border payments
- BIS Working Paper 1385
- BlindPay docs: overview, partner fees, payouts, virtual accounts
- BlindPay: pricing
This article is for general information only and is not legal, tax, or compliance advice.
FAQ
More payments articles
See all payments articlesSmall vs large cross-border stablecoin payments: how payment size changes cost and route
Fixed fees make small cross-border payments expensive in percent. Thin liquidity limits large ones. How size changes cost, compliance, and the right route.
Stablecoin payments business case template: how to pitch cross-border stablecoin payouts to your CFO
A fill-in business case for cross-border stablecoin payouts: cost baseline, proposed flow, cost model, risks, pilot plan, and the decision to ask for.
How to choose a payment processor: a 12-point scorecard for card, bank-transfer and cross-border jobs
Pick a payment processor by the job you need done. A 12-criteria scorecard with weights that sum to 100, a two-week test and a no-downtime switch plan.