Create a payment without wallet cryptogram — with MPI (direct)

When the cryptogram is not available (PAN_ONLY authorization method), 3DS authentication is required. If you have your own MPI (Merchant Plug-In), pass the 3DS authentication results directly — the gateway skips its own 3DS verification and returns a direct response.

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 (FPAN) 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_authentication_valueStringrequired

The 3DS authentication value from the merchant's own MPI

threeds_directory_server_trans_idStringrequired

The Directory Server Transaction ID from the merchant's own MPI. Must be provided together with threeds_authentication_value.

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.

Example RequestHTTP

POST /rest/payment
Authorization: Basic <base64(api_key:api_password)>
Content-Type: application/json
{
"payment_type": "googlepay",
"order_id": "GPAY-67890",
"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_authentication_value": "MDAxMDAxMDAxMDAxMDAxMDAxMDA=",
"threeds_directory_server_trans_id": "f25084f0-5b16-4c0a-ae5d-b24e2f921514"
}

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": "938834bc-769f-44e7-ab25-da9aeaad5346",
"payment_type": "googlepay",
"status_code": 3,
"status": "completed",
"order_id": "GPAY-67890",
"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 without a wallet cryptogram using your own MPI, omit threeds_wallet_cryptogram and pass merchant-side 3DS 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.

Parameter	Test Value
threeds_authentication_value	AUTHENTICATION_VALUE
threeds_directory_server_trans_id	54c64c00-eef8-4a8b-af44-fee8cc57e530
card_number	5286940020000908
card_holder	Max Mustermann
card_expiry_month	12
card_expiry_year	2026