SettleFlow API

Error codes

Full catalog of E-PRO error codes returned by the V1 API

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–27)

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

Transaction & customer (100–113)

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

Exports (150–152)

CodeMessage
150Export failed or being generated, please try again later
151Invalid parameter ChargebackUrl, do not forget protocol
152Invalid 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:

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

Limits (300–302)

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

Currency conversion (400–404)

CodeMessage
400MerchantID currency conversion not supported
401OriginalCurrency must be filled if you want Epro to convert your currency
402OriginalAmount must be filled if you want Epro to convert your currency
403OriginalCurrency conversion is not currently supported
404OriginalCurrency, OriginalAmount and ConvertCurrency are only available on EUR accounts

SMS (500)

CodeMessage
500Error while sending SMS to the customer

How domain errors map to E-PRO codes

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

Domain errorE-PRO code
NotFoundError102
ValidationError103
ConflictError104
UnauthorizedError3
Any other error1

Debugging tips

  • If you get 5 (missing parameters), check that every required field on /docs/payment is present with a non-empty string value.
  • 200222 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.

On this page