SandBox Environment

EdfaPay provides a dedicated sandbox environment, an essential tool for merchants to develop and rigorously test their payment integrations before deploying to a live production setting. This simulated environment accurately mirrors all core functionalities of our payment platform, allowing for comprehensive testing without processing real transactions.


Purpose of the Sandbox

The EdfaPay sandbox environment empowers you to:

  • Simulate Transactions: Test various transaction types, including sale and refund requests.
  • Validate Flows: Verify 3D Secure redirection processes and other payment workflows.
  • Explore Outcomes: Simulate diverse transaction results, such as SUCCESS, DECLINED, and REDIRECT, to understand system responses.
  • Test Webhooks: Evaluate Webhook callback behavior and ensure proper notification delivery.
  • Master Hash Generation: Safely implement and troubleshoot your hash generation logic.

Sandbox Test Account Credentials

Utilize the following sample credentials for testing within the EdfaPay sandbox environment:

FieldValue
client_keysandbox-client-key
passwordsandbox-secret-password
card_number5123450000000008 (MasterCard)
exp_month01
exp_year2039
cvv100
payer_email[email protected]

Important: These test credentials are exclusively valid within the sandbox environment. For live production use, a complete onboarding process and unique credential generation are required.


Hash Calculation in the Sandbox

Even within the sandbox environment, all API requests must be authenticated using a generated hash. The hash generation process adheres to the same rules as the production environment:

const ReverseString = str => [...str].reverse().join('');
const final = (ReverseString(email) + password + ReverseString(cardNumber.substr(0, 6) + cardNumber.substr(-4))).toUpperCase();
const finalHash = CryptoJS.MD5(final).toString();

📘

Key Sandbox Notes

  • No Live Data: Never use live card data or real sensitive information in the sandbox.
  • Use Test Credentials: Always use your test client_key and the sandbox hash key.
  • Webhook Testing: You can simulate webhook behavior by configuring your own endpoint or by leveraging third-party tools like Webhook.site for inspection.