Skip to main content
POST
Test Webhook

Test Webhook

Send a test webhook event to your configured endpoint. This is useful for:
  • Verifying your webhook handler is working correctly
  • Testing signature verification
  • Developing and debugging your integration
All test data is simulated and clearly marked with TEST_ prefixes. These are not real transactions, cards, or cardholders. The only real values are:
  • Your appId
  • The webhook signature (signed with your real webhook secret)

Request

string
required
The event type to simulate. Use List Events to see available events for your app type.

Response

boolean
Whether the request was successful
object

Test Payload Structure

All test webhooks follow the standard webhook format:

Identifying Test Webhooks

Test webhooks can be identified by:
  1. The _test: true field in the data payload
  2. The _note field explaining it’s test data
  3. All IDs prefixed with TEST_
Your webhook handler should check for _test: true if you want to handle test webhooks differently in production.

Available Test Events

Issuing App Events

Collection App Events

Verifying the Signature

Even test webhooks are signed with your real webhook secret. Use this to verify your signature verification code:
Your webhook endpoint must return HTTP 200 within 10 seconds for the delivery to be considered successful.

Authorizations

Authorization
string
header
required

JWT access token obtained from /auth/token

Body

application/json
event
string
required

The event type to simulate. Use List Events endpoint to see available events.

Example:

"card.created"

Response

Test webhook sent

success
boolean
Example:

true

status
integer
Example:

200

message
string
data
object
meta
object