Error codes

Response shape

V1 errors are returned with HTTP 200 and a non-zero Code:

{
  "Code": 206,
  "Error": "Invalid parameter CardNumber, check format or Luhn algorithm"
}

Inspect Code — not the HTTP status — to decide whether a request succeeded. Code: 0 means success.

Authentication & configuration (1–28)

Code	Message
`1`	Invalid request
`2`	Invalid protocol, HTTPS must be used
`3`	Invalid API key
`4`	API key is not supplied
`5`	Missing parameters
`6`	Incorrect merchant configuration
`7`	Oneclick payments not allowed on this account
`8`	3DSecure payments not allowed on this account
`9`	Evoucher purchase not allowed on this account
`10`	Service unavailable
`11`	Server IP address not allowed
`12`	Transaction declined by merchant
`13`	Transaction declined by merchant
`14`	Transaction declined by merchant
`15`	Your account is 3DS only, please use `3DS=yes`
`16`	Your account is VIC only, please use `VIC=yes`
`17`	A payment must be either 3DS or VIC
`18`	VIC payments not allowed on this account
`19`	Oneclick payments not supported on this account
`20`	3DSecure payments not supported on this account
`21`	Incorrect merchant configuration, please contact us
`22`	Maestro cards require 3DSecure
`23`	MasterCard transactions not supported
`24`	iDEAL payments not supported on this account
`25`	Only iDEAL payments are supported on this account
`26`	Prepaid, gift and virtual cards not supported on this account
`27`	Unknown BIN
`28`	Payment method not allowed on this account

Transaction & customer (100–113)

Code	Message
`100`	Client not found
`101`	Can't create client, contact us if the problem persists
`102`	Transaction not found
`103`	Invalid transaction
`104`	TID already used for another transaction
`105`	OneClick payment impossible, no credit card found for the given UID
`106`	ReturnUrl is mandatory with 3DS enabled
`107`	This user is not allowed to make any payment
`108`	No valid credit card found for the given UID
`109`	This user is not allowed to make any payment
`110`	Can't add a card for this client, contact us if the problem persists
`111`	No credit card found for this Alias
`112`	This user is not allowed to make any payment
`113`	This user is not allowed to make any payment

Exports (150–152)

Code	Message
`150`	Export failed or being generated, please try again later
`151`	Invalid parameter ChargebackUrl, do not forget protocol
`152`	Invalid parameter Date, supported formats are YYYY-MM or YYYY-MM-DD

Parameter validation (200–222)

Each field validated by the API maps to a dedicated code:

Code	Message
`200`	Invalid parameter Amount, must be numeric only
`201`	Invalid parameter Uid, must only contain [a-zA-Z0-9-_]
`202`	Invalid parameter Tid, must only contain [a-zA-Z0-9-_]
`203`	Invalid parameter Email
`204`	Invalid parameter Firstname or Lastname, must only contain [a-zA-Z- ] with or without accents
`205`	Invalid parameter ClientIP
`206`	Invalid parameter CardNumber, check format or Luhn algorithm
`207`	Invalid parameter CardMonth or CardYear, month is always composed of 2 digits and year of 4 digits
`208`	Invalid parameter CardCVV, must contain 3 or 4 digits
`209`	Invalid or missing parameter CallingCode, it should be numeric only
`210`	Invalid parameter CardOwner, must only contain [a-zA-Z- ] with or without accents
`211`	Invalid parameter Address, must only contain [a-zA-Z0-9- ] with or without accents
`212`	Invalid parameter ZipCode, must only contain [a-zA-Z0-9- ]
`213`	Invalid parameter City, must only contain [a-zA-Z- ] with or without accents
`214`	Invalid parameter Country, check ISO 3166-1 Alpha-3
`215`	Invalid parameter Phone
`216`	Invalid parameter BirthDate, check format YYYY-MM-DD
`217`	Invalid parameter BirthPlace, must only contain [a-zA-Z- ] with or without accents
`218`	Invalid parameter ReturnUrl, do not forget protocol
`219`	Invalid parameter OriginalAmount, must be numeric only
`220`	Invalid parameter OriginalCurrency, check ISO 4217
`221`	Invalid parameter Alias
`222`	A field your account requires is missing — commonly `Address`, `ZipCode`, `City`, `Country`, `BirthDate`, `Phone`, `Firstname` or `Lastname`. The required set is configured per account; ask your account manager.

Limits (300–302)

Code	Message
`300`	Parameter Amount exceeds the maximum allowed by transaction
`301`	Maximum number of transactions per day per credit card reached
`302`	Maximum amount per week per credit card reached

SMS (500)

Code	Message
`500`	Error while sending SMS to the customer

How domain errors map to E-PRO codes

Internally the platform raises typed errors. They are mapped to E-PRO codes before being returned:

Domain error	E-PRO code
`NotFoundError`	`102`
`ValidationError`	`103`
`ConflictError`	`104`
`UnauthorizedError`	`3`
Any other error	`1`

Debugging tips

If you get 5 (missing parameters), check that every required field on /docs/payment is present with a non-empty string value.
200–222 pinpoint exactly which field is malformed — the code number is stable across versions.
104 ("TID already used") is the sign that your idempotency key collided with a previous attempt. Generate a fresh Tid for retries.
102 ("Transaction not found") on refund/status typically means the Tid / Reference does not belong to your merchant account — check which environment your API key is for.
103 on /v1/refund with an Error starting with "Daily refund limit reached" means your account has a maximum number of refunds per day and it is used up. The counter resets at 00:00 UTC; retrying before then will not help — contact us to have the limit raised or lifted. Refunds initiated by the payment provider are never blocked by it.

On this page