Skip to main content


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 Merchant Paytool Server. Configuration includes following information:

  • Customer name – Basically, it's the name of the Customer shop, company and so on. The following parameter will be displayed to the user in Merchant Paytool form.

  • Description – information about Mechant. The following parameter will be displayed to the user in Merchant Paytool form.

  • Redirect URL’s - Those are the addresses to which user will be redirected after a successful or unsuccessful transaction. These parameters can be static (added to the Client's account configuration) or sent in the order initiating the transaction.

  • 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.

  • Term of use and privacy notes URL – addresses where the Customer stores above-mentioned documents

  • Customer's pictures – These are image that could be, for example, the Customer's logo. They will be posted as requested by Customer in the Merchant Paytool webview. This point is optional. If the Customer does not provide such pictures, the Merchant Paytool will be shown with it's default appearance – find in the “User flow” chapter.

After creating an account for the Customer, Verestro provides all necessary data for Customer which allow to use the solution. After Customer onboarding is done by Verestro partner can start integration with Donate Widget. Such data includes:

  • api key – value that defines a Customer in the context of donation process offered by Verestro. The value api-key should be send by the Customer in every request - Verestro system maps the request with the proper Customer's account. Technical information about the api-key can be found here.

  • basic authorization - it is the login and password of the Customer account in the Verestro system. Basic authorization is needed if the Customer wants to download transaction data via the "get transaction details" method.


If the Customer has chosen to integrate with the One Time Payment API component, he will only receive Basic Authorization which is login and password of the Customer account in the Verestro system. Basic Authorization will be needed for the Customer to be able to perform requests to every method offered by the One Time Payment API.


The Customer must also have to create an account in the Acquirer's system which settles transactions. Such an account is defined by the MID parameter (to find out what MID is, see the "Terminology" chapter). This is a very important parameter as it is required for payment processing. This parameter, together with it's authorization data, can be provided by both the Customer and Acquirer. Verestro offers support in creating such an account 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. For more information about integration see "Technical documentation" chapter.

The solution allows to assign one terminal to Customer account. If the Customer wants to operate several terminals, it requires the creation of additional Customer accounts (account per terminal) or development on the Verestro side that will handle such a requirement. Does not apply to Customers executing transactions using the One Time Payment API.