Documentation
  • Welcome!
  • Card (server to server)
    • Overview
      • Authentication
      • Process Flow
      • API Endpoints
      • Testing
    • API Commands
      • 700 – Start Credit Card charge (3DS Enabled)
      • 701 – Request Capture Authorization
      • 702 – Request Cancel Authorization
      • 708 – Check transaction details
      • 709 – Check transaction status
      • 720 – Credit Request
      • 756 – Manual Rebill Request
      • 760 – Request Refund
    • Notifications
      • Notifications
      • 850 – Transaction state Notification
      • 860 – Refund Notification
      • 880 – Dispute Notification
    • Transaction Status Codes
    • 3D Secure Integration
  • APM Checkout (Blik)
    • Overview
      • Process Flow
      • Testing
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Create a checkout session
    • Retrieve a Checkout Session
    • Webhoook Event Notification
    • Pay a Checkout Session
  • Refund a Checkout Session
  • Retrieve checkout session refund
  • Wallet API
    • Introduction
      • Authentication
      • Metadata
    • Errors
      • Error object
      • Errors type list
      • Decline errors code list
    • Payout
      • Create a payout
      • Retrieve a payout
  • Wallet payment page
    • Payment Page
Powered by GitBook
On this page
  1. Card (server to server)
  2. Overview

Testing

Test cards are meant only for Test/Sandbox environment. You should not use test cards for Production/Live environment. Using test cards on Production/Live environment might result in temporary ban.

Avoid Using Fake or Placeholder Data Like test.com or Test Your transaction may be matched against existing or blacklisted data, and there's a high chance that generic "test" data has already been flagged or used by other merchants.

For each Merchant account, the Merchant will be issued login credentials and URL for the Merchant Back Office on a TEST server. All necessary API documentation and connection information will be located there. The TEST server has the following features to assist in integration:

Good to know: All the methods shown below are to emulate test results

CVV Range
Behavior

001–249

Non-enrolled card – Transaction approved

250–499

Enrolled card (3D Secure) – Approved after ACS auth

500

Simulate transaction error

501–749

Non-enrolled card – Transaction declined

750–799

Enrolled card (3D Secure) – Declined even after auth

Test Cards

Card Number
Card Type
Expiry Date
CVV
Additional Info

4242424242424242

Visa

12/30

123

Classic Visa test card

5454545454545454

MasterCard

12/30

123

Classic MasterCard test

4111111111111111

Visa

12/30

123

General Visa test card

6011000000000004

Discover

12/30

123

Discover test card

378282246310005

American Express

12/30

1234

AMEX test card

3530111333300000

JCB

12/30

123

JCB test card

30569309025904

Diners Club

12/30

123

Diners Club test card

38520000023237

Carte Blanche

12/30

123

Carte Blanche test card

6011601160116611

Discover

12/30

123

Another Discover test card

3566111111111113

JCB

12/30

123

Another JCB test card

Usage Instructions

You can use the card numbers provided above for testing purposes in your development and staging environments. These card numbers will allow you to simulate various payment scenarios without processing real transactions.

By using these testing cards, you can ensure that your payment gateway integration works correctly before going live with real transactions.

PreviousAPI EndpointsNextAPI Commands

Last updated 9 days ago

For additional valid testing card numbers, you can visit sources like . This website provides a variety of test card numbers that you can use to verify the functionality of your payment processing system.

GetCreditCardNumbers