Mock Services
For testing purposes, we have created mocked transactions and events in the sandbox environment. This is possible through a set of static mock responses that can be fetched based on certain request parameters.
Testing transactions in sandboxCopied!
Sandbox mocks
To see a payout status in the sandbox environment, we have mocked payouts transactions to facilitate. You can easily test these scenarios by hitting our GET/transactions/{id}
endpoint with the following IDs:
Payout status |
Mocked transactions IDs |
---|---|
awaiting_deposit |
00000000-0000-0000-0000-000000000000 |
processing |
11111111-1111-1111-1111-111111111111 |
completed |
22222222-2222-2222-2222-222222222222 |
failed |
33333333-3333-3333-3333-333333333333 |
refunded |
44444444-4444-4444-4444-444444444444 |
cancelled |
55555555-5555-5555-5555-555555555555 |
error |
66666666-6666-6666-6666-66666666666 |
For more information about managing transactions, see our Transaction section.
Testing webhooks in sandbox environmentCopied!
Sandbox mocks
In the sandbox environment, we don't send real webhooks. Instead, we provide mocked webhook events for testing. You can trigger these events by making requests to our sandbox endpoint and specifying which event type you want to receive.
To test webhooks in sandbox, send a POST request to the /webhooks/mock endpoint with the desired event_type
(check the events list here). The webhook will be delivered to your registered URL.
Here is a request example in sandbox environment:
{
"event_type": "payout.processing"
}
For more details about webhooks, refer to our Webhook section.