Create a payment without wallet cryptogram — without MPI (3DS required)

When neither a wallet cryptogram nor merchant-side 3DS results are available (PAN_ONLY), the gateway performs 3DS authentication. The response will have status: "pending" and a client_action that the merchant must handle.

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)

Omit threeds_wallet_cryptogram, threeds_authentication_value, and threeds_directory_server_trans_id. The gateway will perform 3DS authentication automatically. 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"
}

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

client_actionString

Indicates the required client-side action. Possible values: postForm (build and submit a POST form using the data in action_data) or redirect (redirect to the url in action_data).

action_dataObject

Contains: url (target URL of the action) and, in case of a postForm, fields (key/value pairs of the data to be posted).

The merchant must build a form on their frontend and POST the fields to the provided url in action_data. This will redirect the customer to the 3DS authentication page. Once 3DS is completed, the customer is returned to the merchant's success_url or error_url.

Example ResponseJSON

{
"transaction_id": "4037b0b4-271b-4486-b7b0-a4569c9ebe40",
"payment_type": "googlepay",
"status_code": 2,
"status": "pending",
"order_id": "123000",
"message": null,
"additional_transaction_data": null,
"amount": 10.0,
"included_fees": "0.00",
"error_code": 0,
"client_action": "postForm",
"action_data": {
  "url": "https://3ds-acs-url.example.com/v1/acs/challenge-initiate",
  "fields": {
    "creq": "eyJ0aHJlZURTU2VydmVyVHJ..."
  }
}
}

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 and without MPI, omit threeds_wallet_cryptogram, threeds_authentication_value, and threeds_directory_server_trans_id. This triggers the gateway 3DS flow.

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
card_number	5286940020000908
card_holder	Max Mustermann
card_expiry_month	12
card_expiry_year	2026

Complete the client_action returned in the response (postForm or redirect) to continue with the acquirer-provided 3DS flow.