Overview
The Sandbox Environment provides merchants and developers with a secure space to test and validate EdfaPay S2S APIs before going live. All requests in sandbox mode simulate real payment flows without processing actual financial transactions.
Using S2S Sandbox APIs, you can test end-to-end scenarios such as:
- Creating and initiating transactions via Server-to-Server
- Checking transaction status
- Capturing authorized transactions
- Processing refunds
- Performing credit void operations
- Managing recurring payments
This ensures your integration is fully functional and compliant before moving to production.
Base URL
https://apidev.edfapay.com
Note: Do not use the production base URL when testing in sandbox.
Available Endpoints (S2S)
Use these endpoints for Server-to-Server integration instead of Checkout APIs:
-
Embedded Card Payment (POST) – Initiate and process card payments via S2S
-
Status (POST) – Retrieve the current status of a transaction
-
Capture (POST) – Capture an authorized transaction
-
Refund (POST) – Simulate a refund for a completed transaction
-
Credit Void (POST) – Void an authorization before capture
-
Recurring (POST) – Test recurring payment setup and execution
Each endpoint has its own dedicated page with request/response examples and usage guidelines.
Best Practices for Sandbox Testing
- Validate all responses against your integration logic before going live.
- Use sandbox test cards and credentials provided by Edfapay.
- Expect timing differences and simulated delays compared to production.
- Thoroughly test webhook/callback handling in sandbox:
- Respond with HTTP 200 OK promptly.
- Keep sandbox and production credentials separate.
- Test partial capture/refund/void flows if your business requires them.