Test Connector
Connect a Provider:
- Supported methods: Card • Native, Card • Redirect, Amazon Pay • Test, PayPal • Test, Apple Pay • Native, Google Pay • Native
- Supported currencies: UAH, USD, BTC
- Industries: Payments
- Geography: Worldwide
Connect Test Provider on our Dashboard
- To connect a Test Provider, navigate to a Payment Hub and click New connection.
- The system redirects you to the catalogue of available Providers. From the list of Providers, choose the Test Provider.
- Use One-click-connect as it initiates adding a Test Provider without any extra steps.
- You can also add a Test Provider manually by entering Test credentials to the required fields and adding Test methods.
You can use a Test Provider to make a Test payment with the help of Test credentials provided in the table below:
Test credentials
| Brand | PAN | Expiry date | CVV | 3DS | Enrollment status | Status |
| Visa | 4000000000000002 | any* | any | yes | ENROLLED |
authorized |
| Visa | 4000000000000200 | any* | any | yes | ENROLLED |
captured |
| Visa | 4000000000020000 | any* | any | yes | ENROLLED |
authorize_failed |
| Visa | 4200000000000000 | any* | any | no | NOT_ENROLLED |
authorized |
| Visa | 4002000000000000 | any* | any | no | NOT_ENROLLED |
captured |
| Visa | 4000020000000000 | any* | any | no | NOT_ENROLLED |
authorize_failed |
| Master card | 5000000000000009 | any* | any | yes | ENROLLED |
authorized |
| Master card | 5123817234060000 | any* | any | yes | ENROLLED |
captured |
| Master card | 5900000000000000 | any* | any | no | NOT_ENROLLED |
authorized |
| Master card | 5009000000000000 | any* | any | no | NOT_ENROLLED |
authorize_failed |
| Master card | 5519283812030000 | any* | any | no | NOT_ENROLLED |
captured |
| Maestro | 5000000000000090 | any* | any | yes | ENROLLED |
captured |
| Maestro | 5090000000000000 | any* | any | no | NOT_ENROLLED |
captured |
Additionally, you can perform the Test payments with already predetermined unsuccessful system Resolutions. Use any card from the table above, apply any Expire date, and enter one of the CVV codes listed below.
| CVV | Decline reasons | Resolutions |
| 999 | General Fatal Error | general_error |
| 998 | Issuer Decline | issuer_decline |
| 997 | Invalid Request | invalid_request_format |
| 996 | Functionality Is Not Permitted | functionality_is_not_permitted |
| 995 | Limit Violation | amount_limit_violation |
| 994 | Invalid Client Account | invalid_client_account |
| 993 | Unable To Determine 3DS Enrollment | unable_to_determine_3ds_enrolment |
| 992 | Provider Fatal Error | provider_fatal_error |
| 991 | Card Is 3DS Enrolled | card_is_3ds_enrolled |
| 990 | Card Is Not 3DS Enrolled | card_is_not_3ds_enrolled |
| 989 | Initiate Fatal Error | initiate_fatal_error |
| 988 | Invalid Card | invalid_card |
| 987 | Unable To Reconcile | unable_to_reconcile |
| 986 | Invalid Amount | invalid_amount |
| 985 | Auth Fatal Error | card_authorization_error |
| 984 | Access Denied | access_denied |
| 983 | Invalid Pin | invalid_pin |
| 982 | Invalid Details | invalid_details |
| 981 | Antifraud Decline | antifraud_decline |
| 980 | Invalid OTP | invalid_otp_code |
| 979 | Invalid 3ds Code | invalid_3ds_code |
| 978 | Vendor Account Not Found | vendor_account_not_found |
| 977 | Invalid CVV | invalid_cvv |
| 976 | Duplicated Transaction | duplicated_transaction |
| 975 | Invalid Credentials | invalid_credentials |
| 974 | Invalid Card Status | invalid_card_status |
| 973 | Card Is Stolen | card_is_stolen |
| 972 | Card Is Lost | card_is_lost |
| 971 | Invalid Terminal | invalid_terminal |
| 970 | Provider Error | provider_error |
| 969 | Lost Or Stolen Card | card_is_lost_or_stolen |
| 968 | Declined | general_decline |
| 967 | Unknown | unknown |
| 966 | Insufficient Funds | insufficient_funds |
Apple Pay testing via a Test Connector
Our platform allows you to test the Apple Pay Payment method through our built-in Test Connector. Follow a step-by-step testing flow to ensure everything works properly without transferring real money.
- Make sure the Test Connector is added and functions as intended.
- Add a test card to your wallet:
4002000000000000. - When creating a Payment Request, use one of the following Amounts to get the specific result and test a system behaviour:
| Amount | Enrollment status | Status |
| 100 | ENROLLED |
authorize_failed |
| 200 | NOT_ENROLLED |
authorized |
| 777 | NOT_ENROLLED |
captured |
| 666 | NOT_ENROLLED |
authorize_failed |
| 555 | ENROLLED |
captured |
- After the Payment Request is created, add a Payment Request ID into the corresponding URL: http://test-applepay.eu.corefy.com/.
- To use an iFrame in a test flow, add the Payment Request ID into the respective URL: https://test-applepay.eu.corefy.com/iframe/.
Google Pay testing via a Test Connector
Google Pay testing via our Test Connector allows you to simulate various payment scenarios without interacting with real Issuers or Acquirers.
- Make sure the Test Connector is added and functions as intended. To learn more, go to the Test Connector guide.
- Add a test card to your wallet:
4002000000000000. - When creating a Payment Request, use one of the following Amounts to get the specific result and test a system behaviour:
| Amount | Enrollment status | Status |
| 100 | ENROLLED |
authorize_failed |
| 777 | NOT_ENROLLED |
captured |
| 555 | ENROLLED |
captured |
| 666 | NOT_ENROLLED |
authorize_failed |
Updated about 1 month ago
What’s Next
