Dash Webhooks
When an action is taken against a card, an event notification is sent to Dash systems from the card processor. Dash processes those events and calls your registered webhook handler endpoints, posting the relevant data so you can update your system.
You can create a single endpoint to handle all webhooks or you can create an endpoint per event if you wish. In the case where you use a single endpoint you can branch your handling logic based on the event name. It is suggested that you always check event names in any case, before processing.
Events
Card Status
POST HTTP/1.1
Content-Type: application/json
{
"event": "card.status.change",
"targetIdentifier": "string",
"subscriptionIdentifier": "string",
"customerIdentifier": "string",
"proxy": "string",
"status": "string"
}
Handle Status Event Webhook – Dash Webhooks API v0.0.1
Card Replacement
POST HTTP/1.1
Content-Type: application/json
{
"event": "card.replacement",
"targetIdentifier": "string",
"subscriptionIdentifier": "string",
"customerIdentifier": "string",
"newCardIdentifier": "string",
"originalProxy": "string",
"newProxy": "string"
}
Handle Replacement Event Webhook – Dash Webhooks API v0.0.1
Environments
Dash web hooks are only available in production currently.
Testing
Since web hook volume can get heavy at times, it is suggested that you load test your architecture in lower environments (DEV/UAT) by mocking payloads and calling your handler endpoints with significant volume. Keep in mind that any API calls that are made by you in production will generate subsequent webhook events and should arrive at your handler(s) shortly after (within seconds).
Web hooks are backed by message queues at both the card processor and Dash, so they are generally very reliable. It is suggested that you also receive these into queues so that no update is lost to a processing failure.
Security
Dash will connect with your web service using HTTPS and the TLS 1.3 protocol. Dash only allows connections to web hook targets with a SSL certificate from a publicly trusted certificate authority currently.