Onboarding
Register in Verestro
The onboarding process takes place mainly on Verestro side. However, in order to perform onboarding, the Customer must provide some information needed to correctly configure account in Token Payment Service. Configuration includes following information:
| Customer name | Basically, it's the name of the Customer's company, his online shop and so on. |
| Postback URL | This is the address to which information will be send to the Customer about the transaction made by a given user. This parameter is not required if the Customer does not want to receive notifications regarding the transaction. For more information about Postback URL please check Use cases chapter. |
| Notification to the user | It is a flag that defines whether e-mail notifications was sent to the User. Such e-mail contains the transaction status, transaction execution date, transaction identifier, date and amount. The Customer decides whether Verestro will send such e-mails or not. |
| Merchant Id (MID) | This ID is represending Customer in Acquirer's system. Customer has to provide the mid information to enable mid configuration in the Verestro system. Required to process transactions and 3DS via Verestro system. Verestro offers support in creating such an account in Acquirer system if it has integration with a given Acquirer. If the client requires transactions to be processed with the participation of a new Acquirer, then Verestro must perform a new integration. The client is then responsible for providing the documentation that Verestro will use during the integration. |
After creating an account for the Customer, Verestro provides necessary data to the Customer. This data is required to use the Token Payment Service API. Such data includes:
| Basic Authorization | Authorization data for Customer which allow to use the solution. Authorization data are the login and password of the Customer account in the Verestro system. Basic authorization is needed if the Customer wants to deposit the AUTHORIZED transaction or to getTransacionDetails. Basic authorization should be provided as Authorization header with Base64 encoded value of login and password. An example of the Authorization header can be found here. |
| Gateway Id | This is a constant and unique value that defines the PSP in the Google Pay™ system. When making a call to get a card token, the Customer transfers this value to Google Pay™ in the request. Verestro is defined by Gateway Id with verestro value. |
| Gateway Merchant Id | This is a unique Customer identifier assigned by Verestro during the onboarding process. This identifier is in the form of a UUID. Verestro understands and uses this to verify that the message was for the Customer that made the request. Customer passes it to Google Pay™. More information about the Gateway Merchant Id can be found in Google Pay™ documentation. |
Authorization data on BETA and PROD environments differ in password. The login and the gateway Id is the same on both environments.
Register in Google Pay™
To use the Token Payment Service solution, it is necessary for the Customer to be registered as merchant in the Google Pay™ system. An unregistered Customer will not be able to get the card payment token from Google Pay. To register merchant account in Google Pay™ visit Google Pay for Business quick start guide or contact Google Pay™ support. After completing registration as a merchant, the Customer will receive an access to Google Pay™ documentation enabling technical integration.
Register as Web Merchant
| Google Pay Web integration checklist | A checklist presenting the Google Pay integration requirements that must be met by the Customer integrating web application |
| Google Pay Web developer documentation | Technical documentation describing web integration with the Google Pay solution |
| Google Pay Web Brand Guidelines | Branding requirements that must be met by the Customer's web application to be able to use the Google Pay solution |
Register as Mobile Merchant
Mobile integration model is work in progress... The solution will be available for mobile merchants soon. This will allow Customers with mobile applications to integrate to the Token Payment Service Solution.
| Google Pay Android integration checklist | A checklist presenting the Google Pay integration requirements that must be met by the Customer integrating mobile application |
| Google Pay Android developer documentation | Technical documentation describing mobile integration with the Google Pay solution |
| Google Pay Android brand guidelines | Branding requirements that must be met by the Customer's mobile application to be able to use the Google Pay solution |