Post webhook payloads to move simulated transactions, payouts, and refunds to their next state.
Some simulator responses leave a resource in a pending state, such as a
transaction marked as capture_pending or a payout marked as processing.
You can move these resources to their next state by posting a webhook payload to
the connector’s webhook URL.To send a webhook, grab the webhook URL for the connector from your dashboard,
and then post a JSON payload with the expected values.The simulator routes each payload using its event field, so every payload must
include an event value that matches one of the supported events below.
The payment_service_transaction_id needs to be set to the ID of the transaction.
The rest of the fields are optional.
To test refund ingestion, simulate a refund that
was made directly with the payment service. Leave out refund_id, and identify the transaction
with one of transaction_id, payment_service_transaction_id, or payment_service_capture_id.
The payment_service_refund_id and amount are required.Turn on Ingest refunds on the simulator connection first, and capture the transaction before
you send the payload.Example payload:
{ "event": "refund.succeeded", "transaction_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "payment_service_refund_id": "REFUND1234567890", "amount": 1299, "reason": "Refunded in the payment service dashboard", "external_identifier": "refund-12345"}