PayXpert - User documentation
XPays: Processing with payXpert a digital wallet payment that you authenticated on your side
This page details what to do when you have authenticated a digital wallet payment externally and you want to send to payXpert the transaction for processing purposes.
Version | Date | Comments |
|---|---|---|
1.0 | Sep 29, 2025 | Initial revision |
1.1 | Jan 21, 2026 | Rewording of the document |
1.2 | - | - |
Summary
Introduction
This document describes the way to use Digital Wallet Payment solutions (also called “XPay”) with PayXpert E-Com gateway when processing the digital wallet authentication on the merchant side without the PayXpert Payment Page.
Context
The PayXpert payment page provides an integrated XPay implementation where the merchant has nothing to do and PayXpert is handling all the exchanges with the digital wallet providers’ servers to proceed with the authentication of the buyer.
Some merchants or payment service providers may have a way of doing this authentication workflow on their side and just need to process the transaction by providing the authentication result only. The following section describes what needs to be provided in that case.
using this setup means that you are already connected to the associated wallet payment solution (XPay), and that you can, on your side, decrypt the payload to retrieve the payment processing data.
When using the payXpert payment pages, this part is already managed by the payment page, which will contact the E-com Gateway with all the relevant information.
Implementation
Authentication data
Handling the digital wallet authentication returns some authentication result data that must then be forwarded to the transaction acquirer.
When doing these steps on the merchant side, this information must be provided through the E-Com Gateway payment API.
The concerned data are:
Digital Wallet Type: The XPay solution you/the cardholder used to authenticate the payment.
Card-related information
Card Number → In the case of digital wallet payments, the real card number is replaced by a tokenized one; it must be provided as a normal card number.
Card Expiration Date → received in the payload from the XPay.
Cardholder Name → received in the payload for ApplePay only.
Digital Wallet Cryptogram: a digital wallet-specific value that is used to provide proof of authentication, binary string encoded as Base64.
ECI: digital wallet specific value that indicates the result of the attempt to authenticate the cardholder.
Acceptor ID: the identifier of the acceptor with the digital wallet payment.
API dedicated fields
To have the complete list of fields to process a transaction, please refer to the official API documentation at: https://developers.payxpert.com/gateway/.
Specific fields are used in the transaction processing low-level API to provide authentication data for a digital wallet; the table below describes these fields.
Digital Wallet API Parameters:
Field name | Description | Requirement | Alimentation |
paymentMeanType | The type of card entry | Optional | In this case → 'digitalWallet' |
digitalWalletType | Type of digital wallet solution
| Mandatory | Only the ‘apple’ value is accepted for now |
cardNumber | The digital wallet tokenized card number | Mandatory | Retrieved from the decrypted XPay payload |
cardExpireMonth | Expiration Month of the tokenized card ('MM' format) | Mandatory | Retrieved from the decrypted XPay payload |
cardExpireYear | Expiration Year of the tokenized card ('YYYY' format) | Mandatory | Retrieved from the decrypted XPay payload |
digitalWalletCryptogram | Authentication Value Base64 encoded (max length 28) | Mandatory | Retrieved from the decrypted XPay payload |
ECI | Result of the attempt to authenticate the cardholder (2 digits) | Optional | Retrieved from the decrypted XPay payload |
digitalWalletAcceptorID | Identifier of the acceptor (max length 105) | Optional | Retrieved from the decrypted XPay payload |