GPayments

Add GPayments to your payments ecosystem

To connect to this gateway, you will need a merchant account with GPayments. You can log in to your GPayments MyAccount page here. To obtain a live merchant account, visit this registration link and fill all required fields.

Step 1: Look up your GPayments credentials

You can find the required credentials in GPayments MyAccount, including your Merchant Name, Merchant ID, Merchant Certificate and CA Certificate. In order to find the first two parameters, follow the Merchants submenu> Merchants > find the parameters in the Details tab:

To find the required certificates, follow the Merchants submenu> Merchants > find the Download buttons in the Certificates tab:

Step 2:  Add GPayments to your payments ecosystem

To connect GPayments to your Paydock account, please follow these steps:

  1. Log into your Paydock Production or Sandbox account;
  2. Navigate to Services from the menu on the left.
  3. Click on the Add New tab from the top of the page.
  4. Select 3DS Services from the Service Group drop-down list.
  5. Select GPayments and click on the Activate button, like so:
  6. There are 2 different 3DS service modes: Direct and Master Merchant. By default, the Use Paydock Master Merchant Account checkbox should be unchecked. You can complete the connection as a Direct Merchant by completing the following fields:
    1. Label - the name you choose to describe this service within your Paydock account.
    2. Merchant Certificate - This is a client certificate to be used for authenticating the merchant during a transaction API call.
    3. Merchant certificate passphrase - This is a corresponding Merchant certificate passphrase.
    4. CACert - This is a CA certificate bundle used for the Authentication API authorisation.
    5. CACert certificate passphrase - This is a corresponding CACert passphrase.
    6. Merchant Name - This is just a name to identify your account within the Dashboard. You can input the same Merchant Name you have in your GPayments Merchants submenu.
    7. Merchant ID - This is your GPayments Merchant ID.
    8. URL - This is the field where you need to specify the base API URL of the service (e.g. https://paydock.api.gpayments.net/).
    9. Select Environment Mode - This describes whether you are connecting to the GPayments Production or Sandbox Environment. Production is used for processing real transactions. Sandbox is used for testing purposes. Please ensure you’re using the correct credentials for the type of environment you're using.
  7. If you check the Use Paydock Master Merchant Account checkbox, you can activate GPayments for your Paydock Master Merchant Account. You can now provide your credentials to connect your Paydock GPayments account, as follows:
    1. Label - the name you choose to describe this service within your Paydock account.
    2. Country - This is a dropdown to select the country of the operation;
    3. Default currency - This is a default currency of the GPayments account;
    4. Merchant Name - this is just a name to identify. You can put something relevant in terms of who is utilizing the merchant account (e.g. your company name);
    5. URL of the merchant’s site - This is an URL link of the merchant's website; 
    6. Providers - This is a list of the payment providers to choose from (Visa, Mastercard etc.);
    7. Select Environment Mode - This describes whether you are connecting to the GPayments Production or Sandbox Environment. Production is used for processing real transactions. Sandbox is used for testing purposes. Please ensure you’re using the correct credentials for the type of environment you're using.
  8. Click Connect. You have successfully connected GPayments to Paydock.
  9. Note: The Use Paydock Master Merchant Account option isn't a default option. Therefore, you need to obtain access permission from the Master Merchant account owner.

    If you would like to connect this service via API, please use this guide.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us