Check the Global Transaction Recorder API reference here.
The PPaaS Payment API allows you to accept any global card payment method in-store from your payment application running on a payment device, in the cloud, or from your payment gateway. All the transactions are saved, this transaction recording will happen after AUTHORIZATION and will be stored until CAPTURE. Services such as Tokenization as a Service are then available to be used to request a token for the PAN.
The transaction recording serves the following use cases:
Replacing a paper ticket with an e-receipt: In the context of a paperless world, the ticket receipt of a transaction is not going to be printed anymore. To replace the paper receipt, an e-receipt should be created.
Loyalty program management enhancement: The centralization of e-receipts is offering the possibility to better trace cardholder transactions.
Card token provider server: Allows to store all card tokens for a specific customer stored token retrieval on request (restricted to the token owner).
Keep proof of offline transactions: After removing the merchant's paper receipt, when there is a need for the merchant to keep proof of offline transactions in instances such as terminal failure, the trace of the transactions must be secured and stored. The transaction details may contain sensitive data, such as the PAN number.
e-receipt request: Provide an e-receipt on consumer request.
To save the external payment transactions, you can use the transaction recorder API, POST Add External Transaction.