Transactions

📘

Before you begin, read the "Getting started" page.

The Wallet Infrastructure (WLW) sends in total 3 requests towards the Wallet Provider (WSP) for each transaction. These API requests must be implemented by the WSPs API:

1. Transaction init (synchronous API request)
2. Transaction result (synchronous API request)
3. Event with transaction result (async event with up to 2 minutes delay)

For details about how you (as the WSP) should create your API to accept these requests, look at the Demo WSP in our API Reference.

Transaction init

This is the initial request from WLW to the WSP for a transaction. The WSP is responsible for directing the payment request to the correct consumer/device. Information that can help the WSP identifying the correct recipient, can be provided in form of CUIDs (claimed user IDs), see Process WLW transaction init request for more details.

📘

The user is not authenticated/verified at this point. Therefore the name "claimed" user IDs.

Transaction result

After a transaction is complete (or has reached its final state), a request is sent to the WSP. This request contains the final status of the transaction. For details, see Process WLW transaction result request

Event (transaction result)

As well as the API request with the transaction result, the WSP will receive a WSP Event with this information once a transaction is complete. See WSP Events for more details and Process WLW events for API integration

Transaction statuses

During the lifetime of a Wallet transaction, the transaction will always have a status according to the once listed below.