Webhooks

Sudo sends events to your webhook endpoint as things happen on your cards and accounts, so you don’t need to poll the API. To add an endpoint, see Set Up Webhooks. Every event has the same shape: a type, the environment (sandbox or production), your business ID, and the affected object in data.

{
    "type": "card.updated",
    "environment": "production",
    "business": "xxxxxxxxxxxxx",
    "data": {
        "object": { "_id": "63edff25e63a129196e34c62", "status": "active" }
    }
}

Events

Event	When it’s sent
`authorization.request`	A card using a gateway funding source is used. Respond to approve or decline it.
`card.balance`	A balance enquiry is made on a card using a gateway funding source.
`authorization.code`	A one-time code (for example, for 3D Secure) is issued for a card.
`authorization.declined`	An attempt to charge a card fails.
`transaction.created`	A card transaction is completed, or a card fee (such as a failed transaction charge) is taken.
`transaction.refund`	A card transaction is refunded or reversed.
`card.updated`	A card’s details or status change: a USD card passes or fails verification (KYC), or the card issuer cancels a card.
`card.terminated`	A card’s balance is returned to your USD settlement account: the card was terminated, or a USD card failed verification.
`transfer.updated`	The status of a transfer changes.

Respond with an HTTP 2xx status to acknowledge an event. For authorization.request and card.balance, your response body is used to answer the request, so reply within 4 seconds. If you set an authorization token in the Dashboard, Sudo sends it in the Authorization header. Webhook requests use POST with a JSON body. You can retry a failed delivery from the Dashboard.

Overview

Getting Started

Cards

Controls

Purchases

Cloud Card

Webhooks

Events

​Events

Events