👋 Welcome to the Aera Wallet Documentation

Welcome! You’re about to explore the Aera Wallet — a powerful, secure, and fully brandable payment solution designed to help you take control of the customer experience at checkout.

Whether you're a retailer, platform provider, or payment service provider, this documentation will show you how the Aera Wallet can:

Streamline in-store and online payments
Reduce transaction costs by routing through optimal rails
Deepen customer loyalty with seamless, app-integrated experiences
Future-proof your checkout journey with tokenized, ID-based payments

This guide gives you everything you need — from integration steps and API access to business model clarity and technical architecture. You’ll find paths tailored for merchants, membership apps, and payment providers alike.

Let’s build something that’s not just functional — but transformational.

Whether you’re a merchant building a Mobile application, a PSP connecting the checkout, or a platform implementing a Wallet Provider, this page will help you understand what’s ahead — and where to begin.

📚 Table of Contents

Contact Aera to Get Started
Get Access to Aera Wallet APIs
Build Your Mobile Application (DPA)
Set Up Wallet Provider (WSP)
Connect Your PSP
Understand Security, Compliance & Test Users
Run Your End-to-End Test
Ready to Go Live?
Continue Your Integration Journey

Step 1: Contact Aera to Get Started

To begin any integration, you’ll need:

A project contact at Aera
Access to our test environment
Onboarding alignment on which roles you’ll play (Mobile app (DPA), Wallet Provider (WSP), Merchant Store (ECR))

If you don’t have an onboarding contact yet, reach out to us.

Step 2: Get Access to Aera Wallet Infrastructure APIs

Your engineering team will receive:

Wallet API credentials (client ID & secret)
SDK access (.aar for Android)
Access to our Wallet API reference

This includes:

Secure session creation
Token exchange
Result handling
Support for cards, vouchers, loyalty, and more

📎 How to Request API Access →

Step 3: Build Your Mobile Application (DPA)

The Mobile app is your customer-facing app. This is where users:

Log in (e.g. via BankID or loyalty ID)
View and manage their wallet
Pay by scanning a QR or through in-app checkout

Your app will embed the Aera Wallet SDK, which handles all secure actions and payment UIs.

📎 What is a Mobile Application (DPA)? → 📎 Quick Start: Integrate Your Mobile Application →

Step 4: Set Up Wallet Provider (WSP)

When the customer scans a QR code at checkout, the Wallet Provider makes sure the payment request is routed to the correct user and device.

As a merchant, you (or your integration partner) will host the Wallet Provider service.

📎 What is Wallet Provider (WSP)? → 📎 Quick Start: Integrate Merchant Pay →

Step 5: Connect Your Merchant Store

The Merchant Store (ECR) is responsible for:

Sending the transaction to the PSP
Receiving transaction results from the PSP

You may already work with a PSP that’s integrated with Aera — or you may build your own PSP-facing connection.

📎 Accepting Wallet Payments in your Merchant Store? →

Step 6: Understand Security, Compliance & Test Users

Security is built-in. Aera handles:

Identity verification (e.g. BankID or ItsMe)
Tokenized card & voucher storage
PCI-DSS and PSD2 compliance

You'll also get:

BankID test user setup
Voucher onboarding credentials (e.g. Monizze test account)

📎 Security & Compliance Overview → 📎 Test Users and Preproduction Setup →

Step 7: Run Your End-to-End Test

Once all roles are connected (Mobile app, Wallet Provider, Merchant Store), you’ll run full E2E tests:

Simulate QR scan → approve → confirmation
Validate card, voucher, and QR payment flows
Ensure correct handling of results and timeouts

Ready to Go Live?

Once your flows are tested and approved, Aera will:

Assign production credentials
Activate live processing
Monitor first live traffic with your team