Trustly-style bank payments

Standard bank transfers often require the customer to manually enter payment details, such as an IBAN and reference number, into their banking portal, which is prone to manual error and slow reconciliation. Trustly-style payments use API-led Open Banking technology to automate this process.

The payment details are pre-populated, the connection is established via an authorised provider, and the merchant receives a real-time notification of the transfer. This automation allows for immediate order processing, whereas traditional transfers might take days to be manually verified by a finance team.

In the card industry, the chargeback mechanism is a consumer protection feature that allows cardholders to dispute transactions through their issuer. For A2A bank payments initiated via PSD2 or Open Banking, there is no equivalent scheme-wide chargeback right.

While a consumer might contact their bank to report fraud, the 'push' nature of the payment means the funds are transferred with explicit consent.

This makes the transactions significantly harder to reverse, providing merchants with a higher level of finality compared to credit or debit card transactions.

Transaction limits for bank payments are generally determined by the specific bank's own transfer limits and the underlying clearing system, such as the €100,000 cap for SEPA Instant in the Eurozone.

However, these limits are often substantially higher than the daily transaction or credit limits imposed on retail payment cards.

Merchants processing high-value orders find this beneficial as it reduces the likelihood of a 'limit exceeded' decline, though the actual available liquidity in the customer's account remains the primary constraint.

No, the merchant does not need an account at every bank. The payment provider or PSP acts as a technical layer that consolidates these connections.

The funds are typically collected into a settlement account managed by the provider or sent directly to the merchant's existing corporate account.

The provider handles the complex task of integrating with thousands of different bank APIs across various jurisdictions, presenting a single integration point for the merchant's checkout and reporting.

Adding bank payments can improve conversion by catering to demographic preferences, particularly in markets like Germany, the Netherlands, or the Nordics where card usage for e-commerce is lower than elsewhere. By offering a familiar banking login, merchants reduce the friction of entering long card numbers.

However, the redirection to a banking app can sometimes lead to drop-offs if the bank's interface is not mobile-optimised. Generally, for high-ticket items, the added security can increase trust, leading to a net positive effect on completed sales.

Yes, these services are typically classified as Payment Initiation Services (PIS) under the PSD2 and the evolving PSD3 framework in Europe. The providers must be authorised and regulated by their national competent authority to access bank APIs.

This regulatory oversight ensures that the provider adheres to strict security standards for handling financial data and that they only initiate payments with the explicit, informed consent of the end-user for each specific transaction.