Easy start with Sandbox

Introduction to Sandbox Environment

The sandbox environment provides a safe, isolated space for developers to test API functionality without impacting live systems or processing real transactions. It simulates the full range of functionality offered by the production environment, allowing you to ensure that your integration is working as expected before going live.

PAY ATTENTION

The sandbox environment operates with mock data, so any transactions processed are not real and won’t involve actual funds.

 

Test data

Sandbox API host

API URLhttps://sandbox-api.coocoopay.com/
API keyFor authorization, use the public key obtained from the Sandbox dashboard or provided by customer support.

 

Sandbox dashboard

URLhttps://sandbox-app.coocoopay.com/
CREDENTIALSIf you would like to receive credentials, please contact our support.

Sandbox webhook public key

Public Download "webhook-shared-public-key-sandbox.pem"

Sandbox webhook public key
-----BEGIN PUBLIC KEY-----
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtpgcPVQ+pyTQRxuIq2zu
6dm8lcA6EnSpGEjpzv4bhPOHboBFcRYdhY3ToqeILE383Zv7bvsWWqLqrSmKqYYz
jo7pILfAWJ6+pPmp4jvMr78aP6eqc2jYxI/+ZXsV5QezU7oVZohihfWV/rq+BbAr
Hhgk25XoX8Rb21KjvMDoAlVThbQ3+xEZKrEG5s/jDMQ7QFmijDlxiLq/1oDlJ8ih
FxJc4wEKjhtlzRBBYq0q+W7b5d1T8VGExLHRwg7XZ4qosQHRTD45r74h2SHjzPvn
2V5OK7UNBAkO5C9fepoitOSrV9w0OZpjPJcZ55VA5qodAEgANQl+6sjN8KSw/Wnm
0QIDAQAB
-----END PUBLIC KEY-----

Request for test

Sandbox request sample
POST /webhook-url/1697633610 HTTP/1.1
Host: example.com
Signature: kxztHjcNqibE/3ijq5mSrdwrJl7PFkcJWA3NqIlqHeb3Nyokj3GlqsVaCD9ytS+L/8jYS5srFIBt3OCknmASyTV6ywMKziU6IV1rayuINN6Qr0nbzOHT8XzFDt8U8h6hjS2r/VmL4OjIvp8aHYDn1OKKf6YwH+fxWxPkHpvlcQNyVoRjTewEtxgtlQCtwWAwCeF2j0SPjAk57FSd+rfg+HF/T574egz6ur+U4IQctaBvbXpURudfZ2PFPxMyagvJpCRi3a2vqo7ADqR0SwThyamWLWDpKTEUeEDZHJpwXQDRRQZ0ifstzBWCLJXRh6rg68MrCUq6HDML0bKqDRXQBg==
{"data": {}, "error": null}

Webhook Verification algorithm

 

Getting Started with the Sandbox

To begin using the sandbox, follow these steps:

  1. Obtain Credentials: After account setup, you’ll receive API credentials specifically for sandbox use. These will be used to authenticate requests in the sandbox environment.
  2. Set Up Test Configurations: Configure the sandbox environment to align with your expected settings, such as time zone (UTC), currency, and other custom preferences (detailed further under Sandbox Settings).
  3. Initiate Test Transactions: With credentials in hand, you can begin executing test transactions and use the test cards provided for a variety of scenarios (see Test Cards section).

API calls link

Start enjoying all the benefits of the sandbox

Get started right copy

API reference

Learn about authentication requests, responses, and example code

View API right copy

 

Use Cases: Acquiring, Crypto Processing

The API supports various use cases to cater to both traditional acquiring needs and crypto processing.

Acquiring Use Case

CAPABILITIESProvides traditional payment processing, allowing merchants to accept payments from credit and debit cards across various currencies. Ideal for e-commerce platforms, service providers, and other businesses requiring secure payment acceptance.
LIMITATIONSTransactions in the sandbox environment are simulated, so no actual funds are transferred. Certain real-world conditions, such as network latency or unexpected errors, may not fully replicate in sandbox mode.

 

Crypto Processing Use Case

CAPABILITIESEnables processing of transactions in major cryptocurrencies, providing merchants with the flexibility to accept digital assets.
LIMITATIONSSandbox crypto transactions are simulations; no real crypto assets are transferred. Availability of certain cryptocurrencies may be limited in the sandbox environment for testing purposes.

 

Test Cards: Success and Rejection Scenarios

To facilitate testing, a set of test card numbers is available. These simulate various outcomes and allow you to verify how the system handles different payment scenarios:

  1. Success Cards: Use these to simulate successful payment transactions. They allow you to test the typical user experience when a payment is approved.
  2. Rejection Cards: These cards trigger specific error codes and rejection responses. Useful for testing the handling of failed payments, such as insufficient funds or fraudulent card scenarios.
USE ONLY TEST CARD NUMBERS BELOW

Never test using real card numbers or card details in your sandbox environment.

 

Test Cards

Test CaseCard NumberExpected Outcome
SuccessfulTransaction Approved
RejectTransaction Rejected

 

Withdrawal IBAN

Test CaseIBAN NumberExpected Outcome
Completed withdrawal UAHTransaction Approved
Completed withdrawal EURTransaction Approved
Rejected withdrawal UAHTransaction Rejected
Rejected withdrawal EURTransaction Rejected

 

Test credentials - сrypto (payout)

Test case (Payout)CurrencyRequisiteExpected Outcome
SuccessfulUSDT (trc20)Transaction Approved
RejectedUSDT (trc20)Transaction Rejected
SuccessfulBTCTransaction Approved

Test checkout

Test checkout

PAY ATTENTION

«Expiration date» and «CVV/CVC2» fields are filled in automatically in test case

Sandbox account (Merchant Portal)

The "Merchant Portal" is the centralized hub for managing your sandbox account and settings. In the portal, you can:

  1. View transaction logs: Track and review test transactions for troubleshooting and validation purposes.
  2. Access test data: All data in the sandbox is simulated, providing a realistic but safe testing experience without impacting live production.

Sandbox settings

The sandbox environment offers customizable settings, allowing you to simulate real-world conditions to the extent possible.

  1. Time zone (UTC): Transactions and logs in the sandbox are timestamped in UTC, ensuring consistency across testing environments.
  2. Supported currencies: Select from a variety of currencies to test currency-specific processing behavior. This helps ensure that the API handles currency conversions and multi-currency transactions correctly.
  3. API credentials: Unique sandbox credentials are required to access the environment.
    INFO
    These credentials differ from production credentials and must be used solely in sandbox mode.
  4. Transaction Management: Transaction types, such as authorizations, captures, refunds, and voids, can all be tested in sandbox mode to replicate different stages of payment processing.

Each of these settings helps simulate real-world usage in a controlled, risk-free environment, enabling you to fine-tune your integration before going live.

PAY ATTENTION

After integration and testing in the sandbox, the only changes needed will be the public key and the production environment URL. All other settings will remain the same.

Are there any inquiries still outstanding?

Our team of experts is available 24/7 to answer all your questions. Feel free to reach out to us at any time, and we will be happy to help you address any inquiries or issues. Your comfort and satisfaction are our priority.

Need help?

Contact support