# A2A Payment

The A2A payment option demonstrates how EGW utilizes the PSD2-compliant payment initiation flow through a connected ASPSP (bank). This method enables direct payment from a customer’s bank account using a strong customer authentication process.

{% hint style="info" %}
In sandbox mode, this flow is fully simulated using a predefined test ASPSP configured for demonstration purposes.
{% endhint %}

### How-to

To try A2A payments in sandbox:

1. Open the Demo Shop - Navigate to “Demo Shop” in the left-hand menu of the Merchant Portal.
2. Select a Product - Choose an item and add it to the basket.
3. Proceed to Checkout -Click “Checkout” to open the EGW Hosted Checkout Page.
4. Choose “Bank Account” - From the available payment options, select “Bank Account” to initiate an A2A payment.
5. Select the Test ASPSP - You will be shown predefined one test ASPSP (bank)  and region. Select it and continue.
6. Redirect to ASPSP Simulation Page - You will be redirected to the one of real ASPSP sandbox portal.
7. Login & Sandbox Selection
   * Choose “Sandbox” as the login environment.
   * Proceed with the simulated authentication process (decoupled SCA via Smart ID).
8. Consent: Access to Account - A screen will appear asking you to confirm access to account information.
   * Select “Smart-ID” as the authentication method. (decoupled SCA).
   * Press “Confirm”.
9. Wait for Redirect - After confirmation, wait 2–4 seconds to be redirected back to the checkout page.
10. Choose Account to Pay From - Back on the checkout page, select the test account you wish to pay from.
11. Redirect to Confirm Payment (Consent Page) - You will be taken back to the ASPSP page for final consent.
    * Press “Confirm” to authorize the payment. (authorization done via Smart ID as a decoupled SCA)
12. Final Redirect - After another 2–4 second wait, you’ll return to the confirmation screen indicating a successful simulated payment.

<figure><img src="/files/tZbugh4GT6zi1dzAYNzE" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

* Only one ASPSP (test bank) is available.
* Payment consent, account selection, and authentication are fully simulated.
* No real funds are transferred.
* This flow is ideal for understanding customer journey and redirection handling.
  {% endhint %}

### Supported SCA Methods (in Production)

Different banks may support different SCA mechanisms. The most common methods include:

* Smart-ID - Common in Baltic countries — app-based authentication with PIN entry
* Mobile ID - SIM-based authentication tied to the user’s phone number
* Biometrics - Fingerprint or facial recognition via banking apps
* SMS + OTP - Code sent via SMS, often combined with a password or PIN
* App-based Push Notification - Confirm the transaction via a secure banking app


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/self-hosted-checkout-page/a2a-payment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.