Here you will find API Specifications, Request/Response Samples, Sandbox Details for all available endpoints and flows, to help you quickly and efficiently integrate our payment solution.

This section contains fields that can influence payment routing configurations

routingGroup

Type: string (maximum 64 characters)
Description: Identifies the customer as part of a specific group used for routing. This parameter enables segregating customers into different routing strategies for customized handling.

kycStatus

Type: boolean
Description: Indicates whether the customer has successfully passed Know Your Customer (KYC) verification.
Possible Values:

• true: KYC verification passed
• false: KYC verification not passed

paymentInstrumentKycStatus

Type: boolean
Description: Indicates whether the payment instrument (e.g., a credit card) associated with the customer has passed KYC verification.
Possible Values:

• true: Payment instrument KYC verification passed
• false: Payment instrument KYC verification not passed

dateOfFirstDeposit

Type: string (ISO 8601 format: YYYY-MM-DD)
Description: Represents the date of the customer's first deposit. The format adheres to the ISO 8601 standard.

depositsAmount

Type: integer
Description: The total amount deposited by the customer, expressed in the base currency of the system (EUR).

withdrawalsAmount

Type: integer
Description: The total amount withdrawn by the customer, expressed in the base currency of the system (EUR).

depositsCnt

Type: integer
Description: The number of deposit transactions made by the customer.

withdrawalsCnt

Type: integer
Description: The number of withdrawal transactions made by the customer.

trustLevel

Type: string
Description: Used to classify customer traffic into primary or secondary streams.
Possible Values:

• ftd: First-Time Deposit traffic
• redep: Redeposit traffic

btag

Type: boolean
Description: Determines a separation of customer traffic.
Possible Values:

• true: Traffic marked as primary
• false: Traffic marked as secondary

affiliated

Type: string (maximum 3 characters)
Description: Specifies affiliate-related configurations for routing.
Possible Values:

• yes: Indicates affiliate-based routing
• no: No affiliate-based routing

The list of mandatory required params may vary according to the paymentType used, see them attached below in the table: Note: please check all details with your Account Manager

Required params per paymentType

apiUrl for different environments should be the following:

apiUrl values

To get the detailed information about processing volumes, reports, transactions, active users i.e., please visit our Merchant Portal with credentials given to you during the integration process:

Merchant Portal URLs

In case if you want to use any specific blockchain under "CRYPTO" payment method, please specify the blockchain value via the payment request using "additionalParameters" object:

"additionalParameters":{ "blockchain": "TRX"}

In order to receive callbacks from our system, you need to specify 'Webhook Url' within website settings under Merchant Portal, or provide 'webhookUrl' parameter in createPayment request. In case if "webhookUrl" is passed within the payment request, it will override the static one configured in the system.

In general, we do support both static and dynamic callbacks, and you can use whatever suits your business better.
To ensure that callbacks are sent from our system, you can generate a Signing Key in your website settings. If the Signing Key is specified, callbacks from our system will include 'Signature' header with HMAC256 hash generated from JSON body and Signing Key.

These states provide a comprehensive overview of the different stages a transaction may go through, allowing for better tracking, management, and resolution of any issues that may arise during the process.

To proceed with testing for all processing flows and cases, you can use our Sandbox environment, keep in mind that the amount should be less than 10000000. For withdrawals and refunds, the limit is 10000. Using card 4000…0002 will emulate 3DSecure scenario, to complete the payment you must enter the expected 3DSecure One-time password.

Test cards

Expiration date - any future.
CVV - any.
3DSecure OTP: 12345

Alternative Payment Methods

Payin Methods

The following methods are supported for payin emulation, without any username/password pair:

• APPLEPAY
• GOOGLEPAY
• MBWAY
• MULTIBANKO
• OPENBANKING

You just have to pass the payment method value within a request, using the following conditions:

• If the amount is greater than 100, the transaction is automatically declined.
• If the amount is 100 or less, the transaction is automatically approved.

Payout Methods

These methods support payout emulation. Use the following example structures for the receiver or additionalParameters fields:

• SEPA

  "receiver": {
    "iban": "HR1723600001101234565"
  }
  

• FPS

  "receiver": {
    "sortCode": "123456",
    "accountNumber": "1234567"
  }
  

• SWIFT

  "receiver": {
    "iban": "HR1723600001101234565",
    "sortCode": "111111",
    "accountNumber": "1234567"
  }
  

• PIX

  "additionalParameters": {
    "cpf_number": "49123456789",
    "pix_key": "49123456789"
  }