Skip to content
Manual

Form Integration

This guide is for merchants with their own Google Pay registration of the Direct type and a PCI DSS certification. The payment form runs on your domain, hosted by Armaghast, and Armaghast tokenizes and authorizes the payment with your Google Pay keys. If you do not have your own Google Pay keys, use the gateway integration instead.

Merchant Payment Domain Registration Process

The merchant payment domain registration process depends on the domain registrar where the payment address is hosted.

We recommend using third-level domains — for example, if your main website is mysite.com, you can register a domain like googlepay.mysite.com for Google Pay.

We don’t have strict technical requirements regarding the domain level or its name format (including the use of abbreviations or shortened forms).

Such limitations are usually dictated by business goals or the registrar’s own policies.

Process of Redirecting DNS of the Payment Domain to the Processing IP

After registering the domain, you need to direct its DNS records to the processing IP addresses. This can be done in one of the following ways:

  • specify an A record in the DNS settings;
  • add TXT or CNAME records if the domain is hosted on Cloudflare.

To get the current list of A records or the necessary TXT/CNAME records, contact your manager. They will provide you with either the processing IP addresses or the exact record parameters that need to be added in your Cloudflare account.

Process of Issuing SSL Certificates for Payment Form Domains

For proper operation of the payment site, you need to provide SSL certificates. There are two options for obtaining them:

  1. Order certificate issuance through your manager.

    In this case, you provide the domain name, after which you’ll need to confirm domain ownership by creating a set of CNAME records in your registrar’s DNS control panel.

    The manager will provide a list of required records.

  2. Issue SSL certificates independently.

    You can use any certificate issuance service, for example: https://cheapsslweb.com.

    After issuance, you need to provide your manager with: private key (usually in .p12 format) and its password; certificate chain, which can be downloaded from the SSL registrar’s website.

Google Pay Merchant Setup Process

All parameters specified during Google Pay Business registration become accessible in the browser via JavaScript and, consequently, are visible to the end user. Therefore, it’s important to use only verified and correct data.

  1. Creating a Business Add a new Business in the Google control panel at https://pay.google.com/business/console/payment/direct/

  2. Website Registration

    1. Specify the payment domain that you registered above
    2. Choose the Direct integration type and attach the PCI DSS AOC (if you don’t have one, request the current AOC from your manager; during verification, a contract between your company and a PCI DSS certified entity may be required, so prepare for signing it in advance)
    3. Attach the required screenshots

  3. Completing Registration and Key Generation

    1. Website approval typically takes no more than a week. After confirmation of all submitted documents, your site becomes active.
    2. Once the site is approved by Google, you can generate keys. Current information on key generation can be found in your Google Pay account. At present, it’s available at https://developers.google.com/pay/api/web/guides/resources/payment-data-cryptography?hl=en
    3. The PCI DSS Certificate has an expiration date and requires renewal upon expiration

Account Setup

To complete the setup in the console, you need to prepare and specify the following data:

  1. Merchant ID: the merchant identifier of the Business that you created in the Google Pay & Wallet Console,
  2. Merchant Name: the name of that Business,
  3. Encryption private key: the private key whose public key you saved in your Google Pay account during key generation.

These parameters must be entered in the bank terminal settings in the Google Pay section.

Additionally: SSL certificates for the merchant’s payment domain must be provided to your manager for infrastructure deployment on the processing side.

After completing all settings, you need to generate a Bearer Token to work with the specified domain.

If the required domain (HOST) is not in the list, contact your manager to add it.

Note: When configuring independently, set the Default card type in Requestor to Google Pay.