What is a Wallet Provider (WSP - Wallet Provider)?

The Wallet Provider (WSP) is the merchant-controlled middleware that enables your customer’s mobile app to receive a Wallet payment request during an in-store checkout.

Think of the Wallet Provider as the messenger between the Aera Wallet Infrastructure and the customer’s Mobile App (DPA) — triggered during QR-based transactions.

It does not initiate the payment. It does not process the payment. It simply ensures that the right user receives the right payment request — instantly, securely, and in the correct context.

How It Fits Into the Wallet Payment Flow

Here's how the Wallet Provider fits into the bigger picture:

1. Merchant Store (ECR) initiates the transaction

2. PSP receives it and forwards it to

3. Aera Wallet Infrastructure

4. Wallet Infrastructure sends the transaction to the Wallet Provider, which:

   • Identifies the user session
   • Routes the transaction to the correct device (Mobile App)

5. The user receives the payment request in their app (Mobile App)

6. User confirms → Wallet Infrastructure → PSP → Acquirers → PSP → Merchant Store completes checkout

📌

The Wallet Provider does not need to touch sensitive data, talk to the Wallet Infrastructure.

What the Wallet Provider Actually Does

Why Is the Wallet Provider Necessary?

The Wallet Provider creates a secure, merchant-specific layer that:

• Allows only your users to receive your checkout requests
• Routes the transaction to the right person based on session ID or loyalty context
• Ensures the Wallet stays decoupled from the POS/PSP logic (Point-of-sale / PSP logic)
• Keeps all sensitive processing within the Wallet backend (PCI-DSS safe)

✅

The Wallet Provider is merchant-specific and scoped — it ensures that your customer, not someone else's, sees your payment requests.

Your Responsibilities as a Merchant

If you operate a Wallet Provider (or work with a vendor that does), you’ll need to:

• Maintain the Wallet Provider endpoint (Aera provides a reference implementation)
• Map transactions from the Wallet Infrastructure to the correct Mobile App session
• Handle timeouts, retries, and cancellations locally
• Align with Aera on the supported payment methods, brands, and contexts

Aera does not host the Wallet Provider — you (or your provider) do.

Real-World Analogy

Think of the Wallet Provider like a mailroom at your company:

• Wallet Infrastructure drops off an envelope (payment request)
• The mailroom (Wallet Provider) knows which desk (device & Mobile app) to deliver it to
• The customer (user) reads and signs it (confirms payment)
• The signed response is sent back via Aera to the origin (Merchant Store)

📎 What’s Next?

• ▶️ Quick Start: Build and Integrate Wallet Provider
• ▶️ What is the Mobile App (DPA)?