PAY BY BANK / A2A
Open Banking payments for online merchants
Bank-direct payments with traceable authorisation, reliable status events and clear reconciliation. For merchants that need to understand the payment path technically and operationally.
- Last expert review
- 30 July 2026
- Reviewed by
- FoxPay Product & Compliance
01Flow
From checkout to confirmed status
Create payment
Set amount, currency, reference and return target server-side.
Authorise at bank
The buyer moves to the bank channel and approves the payment.
Verify status
The order reacts to confirmed server events, not redirects alone.
Reconcile order
Stable references connect payment, shop order and finance process.
02Operations
Status and webhooks are product functions
Idempotency
Repeated requests must not create duplicate orders or bookings.
Signatures
Verify webhook origin and payload integrity server-side.
Retries
Redeliver timeouts and temporary failures in a controlled way.
Monitoring
Ambiguous or long-pending states remain visible and actionable.
03Boundaries
Important product boundaries
Not a card flow
Authorisation and reversal follow different rules from cards.
Bank coverage
Availability depends on market, bank, account type and current provider scope.
Refund process
Refunds need clear beneficiary, reference and status handling.
Recurring
Recurring capability is a separate use case and is not included in every A2A connection.
04Workflow
Reference Pay by Bank sequence
Browser experience and server-side truth are deliberately separated.
- 01
Create
Create a payment with a unique merchant reference.
- 02
Authorise
Buyer consents in the bank channel.
- 03
Return
Browser shows a preliminary result state.
- 04
Webhook
Server confirms the reliable status.
- 05
Reconcile
Match order and finance entry.
05Evidence
Operational readiness
These cases should be testable and observable before go-live.
| Case | Store reaction | Control |
|---|---|---|
| Success | Confirm order | Webhook + reference |
| Abandonment | Keep open/cancelled | No premature fulfilment |
| Delayed | Update asynchronously | Retry + monitoring |
| Duplicate | Process once | Idempotency |
Concrete bank and market coverage is confirmed within the merchant and integration scope.
06FAQ
Frequently asked questions
Answers for the current, expert-reviewed scope.
Is Open Banking the same as card payment?
No. Authorisation, status, reversal and risk characteristics differ, and store logic must reflect that.
Is the redirect enough to confirm payment?
No. A browser redirect can be missing or manipulated. The reliable status is verified server-side.
Which banks are supported?
Coverage depends on market, bank, account type and current integration scope and is confirmed before go-live.