Initiating a Wallet Payment (Merchant store → DemoPSP)

This page explains how Merchant store (ECR) systems can trigger a wallet payment during checkout using Aera’s DemoPSP.

The integration simulates how a live Point-of-Sale (POS) terminal would work with the Aera Wallet Infrastructure — giving you a test environment to verify the flow between your register, the wallet, and the consumer’s app.

What This Does

When a customer chooses to pay using the Aera Wallet at checkout, the Merchant store must send a request to the DemoPSP to initiate the payment. For information about the API see API reference.

Who Should Use This

This flow is designed for:

• Retailers or solution providers who want to integrate Aera Wallet support into their ECR system.
• Product teams who want to test how the payment flow behaves before going live.
• Non-technical stakeholders who want to understand how wallet payments are triggered at checkout.

What to Expect

• The DemoPSP behaves like a real PSP, but it is only used for testing.
• The response includes a paymentReference that’s used to track the payment through the wallet flow.
• You will be able to poll for updates using a paymentReference returned by the transaction initialization call.
• You can also call the DemoPSP to cancel a transaction.

Simulate failures

While authorizing a transaction the DemoPSP will intentionally reject payments with certain "trigger amounts".

📘

Keep in mind that for hybrid payment the amount will be split into separate sub-transactions based on available balance etc.

This makes it a bit harder to hit those "trigger amounts" and you may hit them unintentionally if you do not consider amount categories while creating the request, as well as the available balance for each payment instrument.

Trigger amounts

• Over 10000.00 (Euro) will fail the transaction/sub-transaction during authorization.
• Over 70 (Euro) on Monizze vouchers will fail the transaction/sub-transaction during authorization.
• Exactly 50.50 (Euro) will fail the transaction/sub-transaction during authorization.
• Exactly 51.51 (Euro) will fail the transaction/sub-transaction during capture.

Integration Overview

Here’s what typically happens:

1. Customer is identified in-store (e.g. by scanning a QR code)
2. ECR sends payment request to the DemoPSP
3. Customer approves payment in their app (Wallet SDK)
4. Wallet signs the transaction
5. Result is sent to the callback URL you provided

This lets your register know the final result before the transaction is marked as completed in-store.

What’s Required

See exact field definitions in the API reference .

After Integration

Once you’ve integrated with this flow:

• You’ll be able to test payment scenarios before going live.
• Your ECR will know how to trigger the wallet payment flow.
• The transaction can be linked to your internal order system using the provided paymentReference

Need Help?

Not sure how to structure your ECR integration? Reach out to your Aera business contact.