Pay by Bank and Open Banking Payments: How They Work at Checkout

What pay by bank means

Pay by bank is a payment method that allows a customer to pay directly from a bank account during an online checkout. Instead of entering card details, the customer selects a bank, authenticates in the bank’s app or online banking service, and approves a payment to the merchant.

The payment is generally an account-to-account transfer. In the European Union, the underlying transfer may be a euro credit transfer, including an instant credit transfer where available. The payment experience is usually provided through open banking, a framework that enables regulated third-party providers to connect to bank accounts with the customer’s consent.

These terms describe related but different concepts:

The exact process depends on the country, the banks involved, the payment provider and the type of account. A customer should therefore check the payment confirmation and the merchant’s terms rather than assuming that every pay-by-bank transaction works in exactly the same way.

The main parties involved in a checkout payment

A pay-by-bank transaction normally involves several participants, even though the customer may see only one payment screen.

The payment initiation provider does not normally take possession of the customer’s online banking password. Under the European Union’s revised Payment Services Directive, known as PSD2, regulated providers must use the bank’s authentication process and operate within applicable authorisation and security rules. Customers should still confirm that they are approving the correct amount and payee before completing the transaction.

What happens step by step at checkout

The customer journey can look simple, but several technical and regulatory steps occur in the background.

  1. The customer selects pay by bank. The checkout displays the payment option, the amount and, usually, the merchant or payee name.
  2. The customer selects a bank. The payment service provider presents a list of supported banks or asks the customer to search for the relevant institution.
  3. The customer is redirected or transferred to the bank. Depending on the integration, this may open the bank’s mobile application, its online banking environment or a bank-hosted authorisation page.
  4. The bank authenticates the customer. The customer may use a password, biometric recognition, a one-time code or another approved method. The bank can apply strong customer authentication under the applicable rules.
  5. The payment details are displayed. The customer should verify the amount, currency and recipient before approving the payment.
  6. The bank processes the instruction. The account is checked for issues such as an invalid account, a blocked payment, insufficient available funds or a failed authentication.
  7. The customer returns to the checkout. The payment provider sends a status such as successful, pending, failed or cancelled. The merchant then confirms the order according to its own fulfilment policy.

A payment confirmation page does not always mean that the merchant has received cleared funds. Some transfers can remain pending, particularly where the payment has not yet settled or where additional checks are required. Customers should keep the bank confirmation and the merchant order reference until the transaction is complete.

The role of strong customer authentication

Strong customer authentication, or SCA, is a security requirement under PSD2 for many electronic payments in the European Economic Area. The European Banking Authority’s regulatory technical standards describe authentication based on at least two independent elements from different categories:

Not every transaction is subject to the same treatment. The legal framework includes exemptions and transaction-specific rules, and the bank decides whether an exemption can be applied. A low-value payment, a recurring transaction or a payment to a trusted beneficiary may be treated differently, provided the relevant conditions are met.

Strong authentication does not remove all fraud risk. A customer may still be deceived into approving a payment to a fraudulent recipient. This is why the approval screen matters: it should be checked in the bank’s genuine application or online banking environment, not solely in a message, email or browser pop-up.

How open banking protects account access

Open banking connections are designed to separate payment authorisation from the sharing of banking credentials. In a compliant flow, the customer is sent to the bank to authenticate and approve access or a payment. The third-party provider uses regulated technical access rather than asking the customer to disclose the bank password directly.

Before approving a connection or payment, the customer should examine:

Account information access and payment initiation are not identical. An application that displays account balances may request permission to read information, while a checkout payment requires permission to initiate a transfer. Customers should avoid granting broader access than the service needs.

Regulation differs outside the European Union and the United Kingdom. In the United Kingdom, open banking payment services operate within the framework created by the Payment Services Regulations 2017 and related regulatory requirements. In other countries, terminology, liability rules and bank connectivity can vary. The provider’s authorisation status and the applicable consumer protection rules should therefore be checked in the relevant jurisdiction.

Pay by bank compared with card payments

Pay by bank and card payments both offer electronic checkout, but they have different payment mechanics and customer protections. The following comparison is a practical starting point rather than a substitute for reading the terms of the specific service.

FeaturePay by bankCard payment
Source of fundsUsually a direct transfer from a bank accountA debit or credit card account
Customer actionBank selection, authentication and payment approvalCard details, wallet approval or another card authentication method
Intermediary dispute processDepends on the bank, payment provider and applicable payment lawMay include card-network dispute or chargeback procedures, subject to their rules
ReversalOften requires a refund or a separate return transferUsually processed as a card refund by the merchant
Information shared at checkoutGenerally avoids typing card details into the merchant checkoutCard details or a tokenised wallet credential may be used

A direct bank transfer is not automatically easier to recover than a card payment. A customer who authorises a transfer to the wrong recipient may face a recovery process involving the bank and the payment provider. The outcome can depend on whether the transaction was unauthorised, incorrectly executed or approved by the customer after fraud or manipulation.

Fees, settlement and refunds

The cost of pay by bank can be allocated between the merchant, the payment provider and, in some cases, the customer. A customer should not assume that a payment is free merely because there is no card number. Any customer-facing fee should be shown before approval and assessed under the consumer rules applicable to the transaction.

Settlement timing also matters. A bank payment may be completed quickly, but the merchant’s order system can wait for a final confirmation. A pending status should not be treated as proof that the order has been paid unless the merchant confirms it.

Refunds are normally initiated by the merchant after a return, cancellation or failed fulfilment. The refund may be sent back to the original bank account or through another method agreed with the customer. Unlike a card payment, there is usually no card chargeback mechanism built into the transaction. Before paying, customers should review:

For a business, reconciliation is an important operational issue. The order reference, payment status and bank transaction reference should be matched before goods or services are released. A screenshot supplied by a customer is not a reliable substitute for confirmation received through the payment provider’s system.

The principal risks for customers

Pay by bank can reduce the need to enter card details, but it introduces risks that require attention.

Safer practice is straightforward: start the payment from the merchant’s genuine checkout, avoid links received unexpectedly, verify the recipient and amount in the bank application, never disclose authentication codes to another person, and contact the bank promptly if something appears wrong.

A practical checklist before approving a payment

Customers can use the following checklist at checkout:

  1. Confirm that the website or application is the intended merchant environment.
  2. Check the order amount, currency and any delivery or service charges.
  3. Identify the payment provider and understand whether the transaction is a bank transfer or another payment type.
  4. Select the correct bank and continue through the bank’s genuine application or online banking service.
  5. Compare the recipient displayed by the bank with the merchant details.
  6. Approve only the transaction that matches the order.
  7. Save the payment reference, order number and confirmation screen.
  8. Wait for a final status before assuming that the order has been accepted.
  9. Contact the bank immediately if the payment is unauthorised, duplicated, sent to the wrong recipient or displayed with an unexpected amount.

Businesses using pay by bank should also test failed, pending, cancelled and refunded transactions. Clear customer instructions are essential because a payment method that is technically available but poorly explained can create duplicated orders, support requests and reconciliation errors.

What to do when a payment fails or looks suspicious

A failed payment should not automatically be attempted repeatedly. First, check the bank account, the payment status and whether the merchant created an order. Repeating a payment without checking can create duplicate transactions if the first instruction is still pending.

If the bank shows a completed payment but the merchant does not show the order as paid, keep the references and contact the merchant’s support channel. If the payment was not authorised, or if the customer believes that fraud or manipulation occurred, the bank should be contacted immediately through its official communication channel. The payment provider may also need to be notified.

The applicable reimbursement and complaint rules depend on the facts. An unauthorised transaction, a technical error and a payment that the customer approved after being deceived can receive different legal treatment. The European Commission’s PSD2 framework, national implementing legislation and the terms of the relevant payment service should be consulted for the applicable process. This article does not replace advice from a bank, payment professional or legal adviser.

Frequently asked questions

Is pay by bank the same as a bank transfer?

It usually results in a bank transfer, but pay by bank adds a checkout interface and a regulated payment initiation connection. A customer does not normally need to copy the merchant’s bank details manually.

Does pay by bank expose my bank password to the merchant?

In a properly designed open banking flow, authentication takes place with the bank rather than with the merchant. Customers should not give their bank password or security code to a merchant or an unknown intermediary.

Can a pay-by-bank payment be cancelled?

Cancellation depends on the payment status and the applicable bank and payment rules. Once a transfer has been executed, recovery may require the bank to contact the receiving institution. A refund from the merchant may be the practical route where the order is cancelled.

Is pay by bank safer than paying by card?

Neither method removes all fraud risk. Pay by bank can reduce the need to share card details, but the customer directly approves a transfer and must verify the recipient carefully. Card and bank-payment protections also differ.

Can a merchant release an order immediately?

A merchant should rely on a verified payment status from its payment system rather than a customer screenshot. Pending or interrupted payments should be reconciled before goods or services are released.

Learn more about this: