Pay by Bank: Checkout, Refunds and Settlement Checklist
Reviewed by WeiJun Tang
Last updated: October 21st, 2026
Insights
A merchant operations guide to bank-funded checkout, with provider-scoped examples and a worksheet for launch decisions.
Pay by Bank lets a customer pay a business from a bank account instead of using a payment card.
For a merchant, the launch decision depends on supported banks, customer authentication, payment confirmation and refunds. Reconciliation means matching the order, payment and financial records. Settlement concerns funds owed under the provider agreement; payout is their transfer to the merchant’s bank. Confirm the exact definitions for your route.
Source: Federal Reserve Board, “Pay-by-Bank and the Merchant Payments Use Case” [1] (United States research note, 7 July 2025); Stripe, “Pay by Bank payments” [2] (selected United Kingdom/European product scope). Accessed 19 October 2026.
This guide is for merchant payments leads. United States (US) planning is the main scope; United Kingdom (UK) examples concern different providers and rules. They are not interchangeable specifications. Start with the full alternative payment methods strategy when selecting your method mix.

Keep the checkout journey connected to the payment and reconciliation records.
Separate the checkout label from the payment rail
“Pay by Bank” is a customer-facing description. Account-to-account payments describe a broader movement of money between accounts. The payment rail is the system that processes the transfer. Open banking concerns permissioned access and services; it is not a universal payment rail.
Term | What it helps explain | Question for the provider |
|---|---|---|
Pay by Bank | The checkout method a customer selects to pay from a bank account | Which customer banks, business locations and currencies are supported for this product? |
Account-to-account payment | The broader account-to-account movement of funds | Which rail, initiating party and account types are involved? |
Open banking | Permissioned financial-data access and associated services, including some payment-initiation flows | What consent is requested, by whom, and under which market's framework? |
Underlying rail | The system used to process the bank payment | How does that rail affect confirmation, returns, settlement and operating hours? |
The Federal Reserve research note discusses US deployments using Automated Clearing House (ACH) and instant-payment rails. That is a reason to ask about the actual rail, rather than assuming every bank-funded payment uses the same mechanism. The note is research, not a specification for your provider.
Source: Federal Reserve Board, “Pay-by-Bank and the Merchant Payments Use Case” (US bank-transfer and instant-payment distinction); Open Banking Limited, “What is open banking?” (UK context). Accessed 19 October 2026. Provider questions are an editorial due-diligence aid.
For the UK, confirm the specific open-banking provider, consent flow, participating banks and customer protection process. Do not translate a UK launch checklist into a US availability claim. A familiar payment-method name does not establish that your business can enable it.
What the customer journey should show
In the product documented in Source [2] for the UK and certain European markets, the customer chooses a bank and approves the payment through the bank's mobile app or web portal. That illustrates one flow; test the one your provider actually offers.
Source: the same publisher, “Pay by Bank payments” [2] (its customer flow and market-specific product). Accessed 19 October 2026.

Bank authorization and the merchant's final payment state are separate checkpoints.
- Method selection: explain that the payment comes from a bank account, using the provider-approved label.
- Bank selection: show the banks available for that customer's country and account. Offer a clear exit if the bank is missing.
- Authentication handoff: make the transition to the bank app or web portal understandable.
- Return to checkout: show the known payment state and the next action. Avoid a success message based only on a redirect.
- Order handling: apply the approved fulfillment rule to the provider's authoritative payment result.
- Reporting: give finance a traceable transaction reference and settlement relationship.
Test mobile browser-to-app behaviour, a customer abandoning the handoff, a delayed return and an expired checkout. These are proposed acceptance cases. They are not assertions that every provider exposes identical states or supports every device flow.
Keep banking credentials out of merchant support forms. If a customer needs help authenticating, direct them to the supported bank/provider journey. Support should troubleshoot using safe order and payment references, rather than asking for a bank password.
Compare operational fit with cards, wallets and manual transfers
Decision area | Bank-funded checkout | Existing cards or wallets | Manual bank transfer |
|---|---|---|---|
Customer effort | Review bank selection, authentication and return-to-merchant friction. | Review saved credentials, wallet availability and authentication in your current integration. | Review payment instructions, reference entry and proof-of-payment handling. |
Payment confirmation | Identify the exact state and event that permits fulfillment. | Use the current provider's authorization/capture model; do not substitute bank-payment assumptions. | Define how received money is matched to the correct order. |
Refunds | Confirm supported routes, partial refunds, failure events and fallback controls. | Check the actual provider's refund and dispute process. | Confirm who authorizes and executes a return of funds. |
Finance | Require transaction, fee, refund and settlement references. | Compare against the reporting and reconciliation process already in use. | Measure unmatched receipts and manual investigation work. |
Availability | Confirm business location, bank-account country, bank list and currency. | Check the supported brands, wallets and markets for the merchant account. | Confirm accepted accounts, currencies and transfer instructions. |
Decision test | Can the team handle the exception path as well as the happy path? | What useful customer choice or operational improvement would the new method add? | Would a connected checkout flow remove a measurable manual task? |
Source: the same product publisher, “Pay by Bank payments” [2] (product-specific inputs); Federal Reserve Board, “Pay-by-Bank and the Merchant Payments Use Case” [1] (full-cost and risk questions). Accessed 19 October 2026. The comparison is an editorial framework, not a measured speed, price or conversion benchmark.

Use the comparison to ask specific questions; it does not rank providers or promise savings.
A merchant does not need to replace every existing method to test a useful bank-funded option. Define the customer cohort and order types first. Keep another supported option available when the customer's bank or account is not supported.
Define a payment-state contract before fulfillment
Write an internal state map using the provider's exact event and field names. The labels below describe merchant decisions. They are not a substitute for integration documentation.
Merchant decision state | Evidence to require | Order and customer action |
|---|---|---|
Customer started | Checkout/payment attempt exists | Keep the order unpaid; allow the customer to continue or choose another method. |
Customer authenticated | Bank/provider authorization step completed | Do not infer final receipt of funds from this event alone. |
Awaiting confirmed result | Provider says the attempt is still processing or otherwise unresolved | Show the current state and avoid a second independent collection. |
Ready for fulfillment | The provider-defined authoritative success condition, matched to this order | Apply the approved fulfillment policy and record the evidence. |
Failed or expired | The provider's final failure/expiry condition | Explain the next step and reconcile any later event before opening a new attempt. |
Refund pending or failed | Refund reference and current provider result | Keep the support case open until the return of money is resolved. |
The same document describes a payment that is authorized but does not receive funds within the expected window. Its handling includes a failure result and an automatic return if funds arrive after that failure. Do not assume another provider follows the same route.
Source: the same publisher, “Pay by Bank payments” [2] (proposed merchant controls informed by its documented states), distinguishing authorization, late-funds failure and refund results. Accessed 19 October 2026. Map every row to your own provider’s documented state model.
The test case is useful even without that exact implementation: make the customer return from the bank before the final payment event arrives. Then replay the event. Engineering should be able to demonstrate one order transition and a clear explanation to support.
Refunds and disputes need their own review
Ask for refund documentation before enabling the method. Confirm whether full and partial refunds are supported, where the money goes, which event indicates completion, and what happens when the receiving account cannot accept the refund.
In the same scoped product example [2], refunds return to the initiating bank account. The documentation also describes a failed-refund path requiring the merchant to arrange an alternative refund. These are that provider’s instructions, not a universal guarantee.
Source: the same publisher, “Pay by Bank payments,” Refunds [2] (the same provider’s product only). Accessed 19 October 2026.
Review customer protection and fallback refunds
Do not use “no chargebacks” as shorthand for “no customer protection, fraud, refund or loss risk.” Determine which complaints and unauthorized-payment processes apply to the chosen product and rail. Give support an escalation owner instead of a slogan.
Before approving a fallback refund, require an authorized investigation of the failed original refund. Otherwise support may create a separate bank transfer while the provider refund is still capable of succeeding. The proposed control is simple: one customer obligation, linked attempts, one owner and a reconciled final result.
Compare full operating cost without a savings promise
Avoid a single percentage comparing “bank payments” with “cards.” Request a quote for the actual market, order value, volume and services. Include implementation and the work required to operate the method.
The Federal Reserve research note explicitly cautions against blanket cost-saving claims. Its discussion includes setup, transaction, processor, subscription and receiving-bank fees. That is a useful cost checklist, not a merchant-specific quote.
Source: Federal Reserve Board, “Pay-by-Bank and the Merchant Payments Use Case,” Section 3.1 (US analysis, 7 July 2025). Accessed 19 October 2026.
Use the readiness and cost worksheet to record the quote, its scope and the operational assumptions. Leave unknown values blank. A support-time assumption is not an observed cost until you have measured it.
- One-time work: engineering, bank-flow testing, legal review, reporting and support training.
- Recurring fees: the actual provider's transaction and service charges, including applicable minimums.
- Exception work: pending-payment enquiries, refund failures, duplicate attempts and unmatched settlements.
- Customer effects: method selection, abandonment, completion and contacts for the defined cohort.
A review can still conclude that the method is useful without proving it is cheaper. For example, the team may value a customer-preferred bank option or better reference matching. State the decision criterion in advance so the business case does not change after the test.
Provider due diligence and the launch checklist

Assign an owner and evidence reference to each launch condition.
Area | Acceptance evidence | Owner to assign |
|---|---|---|
Availability | Written business-location, customer-bank country, bank and currency scope | Payments/provider owner |
Customer journey | Desktop/mobile tests, unsupported-bank exit and cancelled-handoff case | Product/engineering |
Payment states | Event and field map, fulfillment condition; duplicate and delayed-event tests | Engineering/risk |
Refunds | Full/partial capability, completion evidence and failed-refund escalation | Finance/support |
Reconciliation | Sample transaction, fee, refund and settlement records matched to orders | Finance |
Customer protection | Approved consent wording, complaint process, liability and privacy review for the selected market | Legal/compliance |
Operations | Support scripts, owner for unresolved money movements and stop conditions | Support/operations |
Source: Editorial launch checklist informed by the cited product documentation and research. It is a proposed acceptance workflow, not a regulatory checklist or assurance of compliance. Prepared 20 October 2026; documentation access dates are recorded per document in the numbered Sources.
Do not proceed because only the checkout test passed. A controlled launch needs a defined customer cohort, approved fulfillment rules, reconciled refund tests and an owner who can stop the method when exceptions cannot be resolved.
What published announcements and customer stories can teach a merchant
A customer story can identify a useful checkout task. It cannot supply your merchant eligibility, payment-state contract or settlement terms. The examples below concern different buying journeys. Read the operating documents before translating either into your own launch plan.
Separate one-off giving from recurring collection
A provider announcement dated 9 January 2024 says the donation platform would use the provider’s one-off bank-payment product alongside Direct Debit for recurring donations. This is a UK-context open-banking arrangement. It illustrates why the first gift and later collections need separate consent and product checks. It does not establish eligibility for a US merchant or every customer bank.
Source: GoCardless, “JustGiving selects GoCardless Instant Bank Pay for open banking payments” [4a], 9 January 2024; page last edited May 2024. UK-context provider announcement, accessed 20 October 2026; not an independently audited implementation result.
Define the alternative-payment handoff
An official customer story reports that lastminute.com introduced Pay by Bank as an alternative when customers encountered card-payment problems. It describes an initial UK launch; other European markets were expansion plans. This is a travel-checkout example, not a rule to collect again after every card failure. Before copying it, define how the original attempt is checked and how support handles an unresolved result.
Source: TrueLayer, “Travel customer story” [5a], publication date not displayed; accessed 20 October 2026. Reported UK deployment and European expansion plans are not a current country-coverage list.
Use the documents to resolve the money questions
Merchant decision | What the selected document establishes | What to obtain for your route |
|---|---|---|
Is this one purchase or a recurring instruction? | The donation-platform provider’s one-off guide [4b] requires the customer to authorise each payment, unlike a Direct Debit mandate. | The product and consent model for this purchase. Do not generalise this one-off flow to every product called Pay by Bank. |
Which event confirms the required funds state? | The travel-checkout provider’s server-notification (webhook) guide [5b] limits | Your actual funds destination, available event and order correlation. Do not assume this webhook exists for an external-account route or another provider. |
What happens after timeout or refund failure? | The UK/European product document [2] describes an authorised payment timing out, with funds arriving after failure automatically returned. Its refunds have separate succeeded/failed outcomes. | Your provider’s timeout, late-money and refund instructions, plus an owner for the unresolved customer obligation. A refund request alone is not completion. |
Sources: the donation-platform provider, “Pay By Bank,” one-off guide [4b]; TrueLayer, “Payment webhooks” [5b]; the cited product publisher, “Pay by Bank payments” [2]. Provider-specific documents, accessed 20 October 2026; no universal rail behaviour is inferred.
Bring back one usable evidence row
Choose the example closest to your buying journey, then ask for documentation for your own product and market. Start a readiness worksheet for one order type. The review sequence below shows which record and next owner to attach; neither customer story supplies those answers for you.
These provider-published third-party examples are not this publisher’s implementation evidence or independently audited results. They establish no customer relationship, partnership, test outcome or product availability for this publisher.
Build one payment-review record before releasing an order
Use the payment-review worksheet to connect the launch checklist to a specific order type. Fill it with document references and proposed controls first. Add observed results only after an approved test or transaction has actually occurred. Keep actual customer and bank identifiers in your secure records.
Complete the record in six passes
- Fix the scope. In Availability and Rail, record the provider product/version, merchant location, customer-bank country, currency and underlying rail. Attach the document and its date. Leave unsupported coverage blank; a product name is not a bank list.
- Map the payment condition. In Payment confirmation, quote the exact server event or field that your provider says supports the chosen order action. Distinguish a customer return, authentication and an unresolved result. Record the internal order state and the owner of the release decision.
- Show the joins and repeat-event rule. In Order matching and Repeated events, identify how the order and payment are correlated. Reference the procedure for duplicate or out-of-order notifications. A second browser visit must not become an independent instruction to collect or deliver again.
- Keep unresolved money open. In Exceptions, record the late, failed or unknown-payment procedure and the escalation owner. If early release is proposed, attach its separately approved risk policy. Such a policy is not evidence that funds arrived or became final.
- Review refunds separately. Link the refund to the original payment and record its current state. For a proposed alternative refund, document the original result, investigation and duplicate-refund controls. A pending refund is still an unresolved customer obligation.
- Hand the finance map to its owner. In Financial matching, show the payment, fee, settlement and payout references with their currencies. Add the refund’s financial treatment where relevant. Ask finance which record closes each join; a payment-status label cannot answer that question.
Source: Original editorial worksheet sequence, prepared 20 October 2026. Product-state questions are informed by the product publisher’s “Pay by Bank payments” [2] (selected UK/European flow, late-funds and refund handling), accessed 19–20 October 2026. US rail distinctions remain scoped to the Federal Reserve research [1]. This sequence is a documentation method, not a universal rail specification.
Give the reviewer a decision, not a completed-looking form
- Missing evidence: name the absent document or observation, the person who will obtain it and the decision that must wait.
- Conflicting evidence: preserve both records and ask the responsible provider or internal owner to resolve the difference. Do not select the preferred answer to make the sheet look complete.
- Ready for review: all requested references and owners are present. The responsible reviewers still need to inspect the material; a filled worksheet is not payment verification or launch approval.
Two synthetic documentation reviews
Made-up case | Declared evidence | Review finding and next step |
|---|---|---|
A: customer returns; release proposed | The only success basis is the browser return. No scoped settlement/finality reference exists, but the record also says “funds final.” | Keep release and finality claims unresolved. Obtain the provider’s state map; a redirect cannot supply either missing fact. |
B: refund pending; alternative proposed | The original refund remains pending, although an alternative-payment approval label was entered. | Ask the refund owner to resolve the original route and duplicate-refund risk. A populated approval field does not prove the approval exists. |
Source: Original editorial synthetic examples, prepared 20 October 2026. No real merchant, provider test, reviewed contract or executed payment is represented.
The downloadable worksheet is a manual review aid. It does not query a provider, authenticate documents, verify money receipt or authorize fulfillment. Keep its current version with the reviewed evidence and record what remains unresolved.
Decide where Pay by Bank fits

Availability, customer fit and operational readiness are separate decisions.
Consider a scoped launch when customer bank coverage is verified, the bank journey is understandable, and your team can demonstrate payment, refund and settlement handling. Keep the method on hold when those conditions are unknown or the provider cannot supply the necessary evidence.
For the wider checkout discussion, review the publisher’s checkout page. Use the contact form to ask about your target markets, banks, currencies and reporting requirements. This guide does not confirm that the publisher currently offers Pay by Bank for any particular market or merchant account.
Editorial scope: HaiPay is a payment-services vendor and may receive related commercial enquiries. This is operational education, not legal or investment advice or a current provider price comparison. US research, UK open banking and the selected UK/European product document [2] retain separate scopes.
Sources
- Federal Reserve Board — Pay-by-Bank and the Merchant Payments Use Case. Byoung Hwa Hwang, research note, 7 July 2025; US payment rails, cost and risk analysis. Accessed 19 October 2026.
- Stripe — Pay by Bank payments. Its selected UK/European product: markets, bank-account payment flow, refunds and late-funds handling; publication date not shown. Accessed 19 October 2026 and reread 20 October 2026 for the public-case module. Not universal rail behaviour.
- Open Banking Limited — What is open banking?. UK consent and open-banking context; publication date not shown. Accessed 19 October 2026.
- GoCardless — (a) Donation-platform announcement, 9 January 2024; last edited May 2024. UK-context one-off gifts versus recurring Direct Debit; an announcement, not independent performance verification. (b) One-off Pay By Bank documentation, publication date not displayed. The selected individually authorised flow, not every recurring product. Both accessed 20 October 2026 Coordinated Universal Time (UTC).
- TrueLayer — (a) Travel customer story, publication date not displayed. Initial UK launch; listed European countries are expansion plans in the story. (b) Payment webhooks, publication date not displayed.
payment_settledonly for closed-loop payments; the optional settlement-stalled webhook is disabled by default. Both accessed 20 October 2026 UTC.
FAQ
No universal timing follows from the label. Confirm the rail and provider-defined final payment condition, then distinguish that from settlement and merchant payout.
No. Pay by Bank describes a bank-funded payment experience. Open banking covers permissioned access and services; some payment flows use it. The market and product determine the implementation.
That needs a scoped quote and operating-cost comparison. Include setup, provider fees, exception handling and reconciliation. The Federal Reserve research note cautions against blanket savings claims.
Check the product documentation. The product in Source [2] supports full and partial refunds and documents a failed-refund path. Do not assume the same route or capabilities for another provider.
Use your provider's authoritative payment result rather than inferring success from the customer's return. The product in Source [2] has a scoped late-funds case where an authorized payment can still fail.
Do not treat the absence of a card chargeback process as an absence of complaints, unauthorized-payment issues or financial risk. Review the selected product, rail and applicable customer protections.
No availability should be assumed. Verify business location, customer bank-account country, supported banks, currency and account-specific product access.
No. It provides an evaluation workflow. Ask the payment provider to confirm the actual target market, bank and merchant-account scope before making an implementation commitment.