> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/guides/sandbox/test-scenarios/demo-store-and-hosted-checkout/pay-by-bank-payer-authentication-sca.md). # Pay by Bank: payer authentication (SCA) Test the Pay by Bank payer authentication flow in the Sandbox. This scenario tests a Pay by Bank payment that requires Strong Customer Authentication (SCA). The exact screens and sequence depend on the selected bank. Some banks request account-access consent before account selection. Others combine consent, authentication, and payment approval into fewer screens. Start the Pay by Bank flow in either of these ways: * In Checkout UI, select **Bank account** as the payment method. * Create a bank checkout session through the [*Create bank checkout session*](/api-reference/merchant-api/payments/checkout-sessions/bank-checkout-sessions.md#post-egw-version-payments-paymentid-sessions-bank) operation in the [Merchant API](/api-reference/merchant-api/payments/checkout-sessions/bank-checkout-sessions.md#post-egw-version-payments-paymentid-sessions-bank). Then open the URL returned in `scaRedirect`. Checkout UI opens at the bank selection step. ## Bank Selection The payer selects their region and bank in Checkout UI:

Pay by Bank flow: selection of Region and Bank.

After the payer selects a bank, the bank controls the remaining authentication journey. The browser usually redirects to that bank's Sandbox page. ## Authentication at the bank's page In this example, Swedbank opens its SCA page. The payer selects `Smart-ID` and enters test credentials:

Strong Customer Authentication (SCA) example.

Authentication and approval screens vary by bank. The bank may request an additional approval after authentication:

Additional steps after SCA, bank specific.

## Account Consent and Selection Some redirect steps may be omitted when SCA has already completed in the current session. For example, the bank may have issued an access token, consent ID, or equivalent bank-specific credential. This lets the E-commerce Gateway access the payer's data without repeating SCA. Some banks require account-access consent before payment initiation. The payer is then redirected to the bank's consent approval page.

After the E-commerce Gateway obtains consent, Checkout UI displays the payer's eligible bank accounts. The payer selects the account to use for payment.

Account Selection screen at the Checkout UI.

## Payment Approval The E-commerce Gateway sends the payment initiation to the bank through Open Banking. The payer is then redirected to the bank's payment approval page.

After the payer approves the payment, the browser returns to the final Checkout UI screen.

Payment flow end screen at the Checkout UI.

{% hint style="info" %} The redirect back to Checkout UI provides a clear end to the payer journey. The payment status remains controlled by E-commerce Gateway communication with the bank through its Open Banking Aggregation function. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecommerce.seb.ee/guides/sandbox/test-scenarios/demo-store-and-hosted-checkout/pay-by-bank-payer-authentication-sca.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.