Two flows that matter today
A2A push payments and PIS (Payment Initiation Service) for authorised customer-to-merchant transfers. Both authenticate inside the customer's banking app and settle in seconds.
A practical guide to open banking in travel — A2A payments, payment initiation (PIS), the cost picture versus cards, reconciliation, and how open-banking fits alongside card and BACS rails for deposits, balances and supplier payouts.
Open banking is the framework that lets a regulated third party (a payment initiation or account information provider) move money between a customer's bank account and a merchant's account, with the customer authenticating through their banking app. For travel businesses, it is the cheapest customer-payment rail available - if the flow fits the booking. The trick is knowing which flow does.
A2A push payments and PIS (Payment Initiation Service) for authorised customer-to-merchant transfers. Both authenticate inside the customer's banking app and settle in seconds.
Open banking in the UK runs under PSD2 and the FCA's PISP/AISP regime. Customers authenticate inside their banking app — there is no card data, no 3DS challenge, no chargeback equivalent.
Lower cost and faster settlement on one side; manual refund/dispute paths and no liability shift on the other. The art is knowing where the trade-off is worth taking.
A2A payments move money directly between the customer's bank account and the merchant's bank account, authenticated through the customer's banking app. For travel, that lands best on transactions where the customer is already trusted and a 3DS step-up would be friction without benefit.
When a repeat customer is paying a £4,000 balance for travel they have already deposited on, A2A removes the card cost (often a £60-£100 saving), the 3DS step-up risk and the chargeback exposure - in exchange for a single authentication tap in the customer's banking app.
For late bookings where supplier deposits are due before card settlement would arrive, A2A Faster Payments lands money in seconds rather than two or three business days. That timing can be the difference between holding the booking and losing it.
Customers under 40, especially those who already use open-banking for utilities, rent or other regular payments, often prefer the bank-app flow to a card form. Offering A2A as an option meets that preference and reduces card-fee exposure.
PIS (Payment Initiation Service) is the open-banking flow for one-off authorised transfers from a customer to a merchant. The customer authenticates in their banking app, confirms the amount and the reference, and the payment is initiated immediately.
PIS captures the booking reference at the moment of consent — so when the payment arrives, it is already attached to the booking rather than landing as an unidentified bank-statement line.
The bank-app authentication step is the SCA equivalent for open banking. It is built into the rail, so there is no separate step-up risk.
PIS payments are not reversible the way card payments are. The customer has authorised a specific payment to a specific merchant for a specific reference; there is no equivalent of a chargeback. Refunds and disputes are handled directly with the merchant.
Open banking has no chargeback equivalent and no card-network refund mechanic. That changes how travel businesses handle the customer side of a refund - in some ways it is cleaner, in others it asks the operator to do more.
There is no "refund this transaction" button the way there is on card rails. The operator initiates a Faster Payment or BACS credit back to the customer's account, captures the customer's bank details for the return, and records the refund against the original booking and original payment for the audit trail.
Because the customer authenticated in their own banking app, the strongest evidence of authorisation already exists - and lives with the open-banking provider rather than being reconstructed from acquirer logs. Refund discipline replaces representment as the primary dispute path.
Under the PSR's APP fraud reimbursement framework, banks reimburse some categories of customer fraud loss. Merchants who follow the right consent and confirmation flow are not the counterparty, but operators should understand the framework - particularly where a customer claims a payment was authorised under deception.
Open banking is the cheapest customer-payment rail you can run. The economics are striking for high-value travel transactions, but the comparison needs to be honest about the operational cost of running multi-rail.
A2A/PIS fees are usually flat (e.g. 20-60p per transaction) versus a percentage MDR on card. For a £4,000 balance, that is a £60+ saving every time.
Open-banking transactions sit outside the surcharging ban that applies to consumer cards. You do not need to recover the rail cost from the customer because the cost is materially lower.
Faster Payments settle to the merchant within seconds rather than the 2-3 business day card settlement cycle. That improves working capital before considering the cost saving.
Open-banking payments arrive as Faster Payments bank credits rather than card settlement files. That changes the reconciliation pattern - simpler in some ways, different in others.
Unlike card settlement where many transactions arrive bundled in one acquirer file, open-banking payments arrive individually with the booking reference captured at consent. Reconciliation becomes per-payment matching rather than batch unpacking.
Card settlements arrive net of interchange, scheme fees, processor fees and acquirer markup. Open-banking arrivals are gross - the provider fee is billed separately on a different cadence, often monthly. That simplifies the per-transaction picture but requires the provider invoice to be reconciled separately.
Card reconciliation has to unpack interchange, scheme and processor fees per transaction. Open-banking reconciliation is closer to bank-statement matching - one credit per payment, one separate provider invoice on a different cadence. The audit picture is simpler.
Open banking is regulated under PSD2 and overseen by the FCA. The consent and dispute model is fundamentally different from card and changes what evidence merchants need to keep.
All authorisation happens in the customer's banking app under SCA. Merchants never touch credentials. Consent evidence comes from the PIS/AISP provider, not from the merchant.
There is no chargeback mechanism in open banking. Customer disputes are handled merchant-side, with the bank-app authentication record as the strongest evidence of authorisation.
Under the PSR's APP (Authorised Push Payment) fraud reimbursement rules, banks reimburse customers in some fraud scenarios. Merchants who have followed the right consent flow are not the counterparty - but the framework is worth understanding.
felloh treats open banking as a first-class payment rail alongside card, payment links and embedded checkout. The booking-level ledger handles A2A, PIS and VRP the same way it handles any other rail.
Customers receive a felloh payment link and can choose card or open banking at the point of paying. The booking-level evidence is captured regardless.
See payment linksWhere customers prefer card for the deposit and open banking for the balance, both flows land against the same booking with the same level of evidence.
See payment plansOpen-banking arrivals match to bookings the same way card settlements do - one booking-level ledger across rails, not separate workflows.
See reconciliationBring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.