What is a PSP in the Aera Wallet Flow?

A Payment Service Provider (PSP) is the party responsible for handling the actual payment processing in the Aera Wallet ecosystem.

The PSP connects the merchant’s cashier system (ECR) with the Aera Wallet Infrastructure, and ultimately routes the transaction to the relevant payment network (e.g. Visa, Mastercard, BankAxept, vouchers).

In short:

✅

The PSP connects the point of sale to the payment rails — securely and reliably.

Where the PSP Fits in the Wallet Flow

Here’s how the PSP operates during a Wallet transaction:

1. The Merchant Store initiates a transaction (after scanning a QR code)

2. The PSP receives the transaction from the Merchant Store

3. The PSP forwards it to the Aera Wallet Infrastructure

4. The Wallet Infrastructure delivers it to:

   • The Wallet Provider (WSP), which routes it to the user’s app
   • The Mobile App (customer’s app) for review and approval

5. After the user confirms, the signed transaction flows back to the Wallet Infrastructure, then to the PSP, and finally to the cashier system.

🔒

The PSP acts as the entry and exit point for all in-store Wallet transactions.

What the PSP Does (and Doesn’t)

🧠

PSPs do not integrate with the Mobile app or Wallet Provider. They communicate with Cashier system and Wallet Infrastructure only.

PSP Integration Requirements

If you are a PSP (or partnering with one), the integration steps typically include:

• Receiving the transaction initiation from the Cashier system (via Point-Of-Sale software)
• Forwarding the transaction payload to Aera’s Wallet Infrastructure endpoint
• Handling the asynchronous response with the signed result
• Returning the success/failure to the Cashier system
• Supporting routing logic for different schemes (cards, vouchers)

⚠️

PSPs do not require a direct connection to the Mobile app or the Wallet Provider layer. All flows pass through the Wallet Infrastructure.

Compliance & Security

As a PSP, you're responsible for:

• Complying with PCI-DSS requirements (card present / card not present, depending on setup)
• Ensuring transaction IDs, timestamps, and merchant context are included in the request
• Handling retries, reversals, and timeout scenarios gracefully
• Storing logs for dispute resolution and auditing

Aera Wallet ensures:

• No sensitive data touches the Cashier system
• The user confirms and signs every transaction from their own device
• Tokens and keys are securely issued and verified

Common Use Cases

• A PSP provides a single integration to Wallet functionality for multiple merchants
• A PSP routes card and voucher payments through their existing acquiring stack
• A PSP works with multiple Point-of-Sale/Cashier system vendors to ensure Wallet flows are supported across all in-store setups

📎 What’s Next?

• Understand the Mobile App (DPA) Role