Skip to content

Testing assets

This section provides all the necessary resources to support your integration testing with SIBS Gateway. 

It includes credentials, test payment instruments, and scenario simulation guidance to validate your integration before moving to production.

1. Testing Credentials 

To start testing your integration, your onboarding process must be completed with your Account Manager. 

Once completed, you will receive your testing credentials:

  • Terminal Code  
  • Bearer Token  
  • Client ID 
What you can do with your test credentials

With a valid test account, you can:

  • Onboard merchants digitally (Payment Facilitator flows) 
  • Start integration testing flows 
  • Access SIBS Gateway features and APIs 
  • Execute test payment scenarios.
Notification

 Note: 

Test environments simulate real processing flows but do not trigger real financial transactions.

2. Testing Cards 

Use the following card data to simulate payment scenarios in the test environment. 

These cards are not linked to real accounts and do not generate real transactions.

BrandCard numberExpiry dateCVC/CVV3DS3DS Authentication password
Visa417666000000010012/28597Yes (Challenge)123456
Visa476134000000003512/28536No
Mastercard518552005000001012/28001Yes (Challenge)123456
Mastercard520474000000100212/28100Yes (Frictionless)
Mastercard520636100000135112/28536No
Cartes Bancaires Visa4970 4178 0960 982312/28914Yes (Frictionless)
Cartes Bancaires MasterCard5134 1486 5519 781712/28419Yes (Challenge)123456
Cartes Bancaires Visa4010 0562 0000 001812/28123Yes (Frictionless)
Cartes Bancaires MasterCard5137 2100 0000 001812/28123Yes (Challenge)123456

3. Response Simulation & Behavior 

The test environment allows simulation of different transaction outcomes depending on the payment method and input values. 

BLIK Negative Scenarios

To validate robust error handling, you can simulate specific decline scenarios for BLIK and Card payments. Use invalid 6-digit codes (BLIK). 

Payment MethodDecline ReasonStatus CodeDescription6-digit code
BLIK ALIAS_DECLINED E0110 Transaction rejected by financial institution 912111 
BLIK TAS_DECLINED E0201 Declined operation 927111 
BLIK USER_DECLINED E0110 Transaction rejected by financial institution 934111 
BLIK SEC_DECLINED E0201 Declined operation 969111 
BLIK SYSTEM_ERROR E9999 SIBS internal error 956111 
BLIK GENERAL_ERROR E9999 SIBS internal error 961111 
BLIK INSUFFICIENT_FUNDS E0112 Transaction failed due to insufficient funds or exceed limits 960111 
BLIK TIMEOUT E0111 Transaction has expired 989111 
BLIK LIMIT_EXCEEDED E0112 Transaction failed due to insufficient funds or exceed limits 990111 
BLIK USER_TIMEOUT E0111 Transaction has expired 949111 
BLIK ISSUER_DECLINED E0110 Transaction rejected by financial institution 902111 
Card Negative Scenarios

To validate robust error handling, you can simulate specific decline scenarios for Card payments. Use predefined transaction amounts to trigger specific decline response. 

BrandDecline ReasonStatus CodeDescriptionAmount
Visa & Mastercard Exceeds withdrawal frequency E0109 Invalid request, requires authentication 65.65
Mastercard Exceeds withdrawal limit E0761 Transaction exceeds cardholder allowed withdrawal limit 40
VisaSuspected fraud E0759 Transaction declined due to suspected fraudulent activity 15
Mastercard Invalid transaction E0712 Transaction not allowed under card terms 120 
Mastercard Suspected fraud E0759 Transaction declined due to suspected fraudulent activity 144 
Visa & Mastercard Incorrect PIN E0755 Cardholder entered an incorrect PIN 110 

4. ISO Code References

Codes are used across SIBS Gateway APIs as standard identifiers for countries, currencies, and languages. 

They ensure consistency across onboarding, transaction processing, and reporting flows. 

DomainISO Standard
Country ISO 3166-1 Alpha-2 (numeric for onboarding API) 
CurrencyISO 4217 Alpha-3 
LanguageISO 639-1 
Privacy Overview
blank

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

Strictly Necessary Cookies

Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.