Accept Google Pay

MintCash supports Google Pay wherever the underlying provider does. How you integrate depends on the Payment Provider abilities. This guide walks through what it requires of you, the integration paths, and what to consider during testing.

Before you start

You need a Payment Provider with the Google Pay service enabled, Google Pay Merchant ID / Gateway ID and credentials wired up on their side. Then, provide these credentials to your account manager and that's it. All the configuration will happen on MintCash side.

Integration

Once your account manager configures your account, the Google Pay button is rendered on the Hosted Payment Page by default (default or customized HPP). Every payment or subscription you create via the API, will display the option to proceed with Google Pay through our platform. Decryption can happen on the provider's side or ours, depending on the provider's capabilities. The integration you write is the same either way.

1. You send the invoice request to MintCash; we respond with the HPP redirect form.
2. The HPP displays the available payment methods, including Google Pay.
3. Google Pay authenticates the customer and returns the encrypted data.
4. The data is decrypted — by us, or by the provider, depending on the terminal.
5. We create the purchase request and pass the card data to the provider/acquirer.
6. If the acquirer requires extra verification (3DS or OTP), the customer sees the issuer's verification page.
7. We finalize the transaction with the issuer's 3DS response.
8. We send a callback to your backend. If no callback URL is set, we expect a status request from your server.

What differs between the two decryption modes

The thing that changes is whose credentials we use, and that's handled in the terminal configuration we set up for you:

• Decryption on the provider's side — the provider supplies all the credentials, including their Google Pay Merchant ID and Gateway ID.
• Decryption on the MintCash side — you use your own Google Pay Merchant ID and Gateway ID, plus the provider's API credentials. We enable the platform gateway on the terminal.

In both cases your integration is unchanged: create the payment, redirect to the HPP, fulfil on the webhook.

What to test

Run each flow you plan to ship in sandbox before going live:

• Happy path — a Google Pay authorization that lands on payment.succeeded / processed.
• 3DS challenge — confirm ACS flow works as expected and finalize successfully.
• Webhook delivery — confirm your endpoint receives the final callback.