Create a payment with wallet cryptogram (no 3DS required)

When the decrypted Google Pay token contains a cryptogram (CRYPTOGRAM_3DS authorization method), pass it along with the card data. No 3DS authentication is needed.

POST/rest/payment

Production URL

https://api.betterpayment.de/rest/payment

Test URL

https://testapi.betterpayment.de/rest/payment

payment_typeStringrequired

googlepay

order_idStringrequired

Any alphanumeric string to identify the Merchant's order

amountFloatrequired

Amount of the transaction including all taxes and shipping fees

currencyStringrequired

3 letter currency code

postback_urlStringrequired

The URL for updates about transaction status are posted

success_urlStringrequired

Where to redirect the user after a successful transaction

error_urlStringrequired

Where to redirect the user after a failed transaction

card_numberStringrequired

The card number (DPAN) from the decrypted Google Pay token

card_holderStringrequired

Name of the cardholder

card_expiry_monthStringrequired

Expiry month of the card (1-12)

card_expiry_yearStringrequired

Expiry year of the card (4 digits)

threeds_wallet_cryptogramStringrequired

The cryptogram from the decrypted Google Pay token

threeds_wallet_cryptogram_eciString

The ECI indicator from the decrypted Google Pay token

This example includes only the minimum required parameters to create a Google Pay payment with cryptogram. The optional processing parameters from Cardholder Data Parameters such as card_entry, charge_order, clearing_mode, clear_after, and sca_exemption_request are also accepted in this flow. See the Create Payment API reference for the full list of supported parameters.

Example RequestHTTP

POST /rest/payment
Authorization: Basic <base64(api_key:api_password)>
Content-Type: application/json
{
"payment_type": "googlepay",
"order_id": "GPAY-12345",
"amount": "25.90",
"currency": "EUR",
"postback_url": "https://your-postback.url.com",
"success_url": "https://your-success.url.com",
"error_url": "https://your-error.url.com",
"card_number": "4761070000000509",
"card_holder": "John Doe",
"card_expiry_month": "12",
"card_expiry_year": "2026",
"threeds_wallet_cryptogram": "AgAAAAAABk4DWZ4C28yUQAAAAAA=",
"threeds_wallet_cryptogram_eci": "07"
}

Payment API Response

transaction_idString

ID of the created transaction

payment_typeString

Payment type of the transaction

status_codeInteger

Status code of the transaction

statusString

Status of the transaction

order_idString

Order ID of the transaction

messageString

Optional additional information about the transaction result

included_feesString

Included fees for the transaction

error_codeInteger

Error code for the response

Example ResponseJSON

{
"transaction_id": "d1bf9fdf-7268-406f-9e08-8d5a9540ab97",
"payment_type": "googlepay",
"status_code": 3,
"status": "completed",
"order_id": "GPAY-12345",
"message": null,
"included_fees": "0.00",
"error_code": 0
}

Postbacks

For the full list of payment postback fields, see the Payment API. For retry policy and signature verification, see Postbacks.

Test Data

To learn how to add test cards for testing Google Pay, please review the official Google Pay test documentation.

For testing Server-to-Server Google Pay transactions with a wallet cryptogram, use the following test data.

info

The card data in Server-to-Server Google Pay transactions is actually token data (DPAN), not the real card number — but it follows the same format. CVV is not required for wallet token transactions.

info

3DS is more common for Google Pay than for Apple Pay, especially when using the PAN_ONLY authorization method where no cryptogram is available.

The transaction will go straight to completed status.

Parameter	Test Value
threeds_wallet_cryptogram	Af9x2zAAAAABBBCC1XYCMAABAAA=
threeds_wallet_cryptogram_eci	05
card_number	5286940020000908
card_holder	Max Mustermann
card_expiry_month	12
card_expiry_year	2026