Webhooks

Overview

Webhooks let your application receive real-time notifications when events occur — a card charge completes, a recurring payment fails, an invoice is paid. Instead of polling the API, Dime Payments pushes event data to a URL you specify.

Setting up a webhook

Log into the Dime Payments dashboard
Navigate to Advanced > Webhooks
Click Add Endpoint
Enter your publicly accessible HTTPS URL
Select the event this endpoint should receive
Save

Your endpoint must return a 200 response within 3 seconds or the attempt is considered failed. Do any real work asynchronously — acknowledge the delivery first, then process it on a queue.

One endpoint per event

Dime Payments registers each webhook against a single event. Payloads do not carry an event-name field, so you cannot inspect the body to tell which event fired. Instead, register a separate endpoint URL for each event you care about and identify the event by which URL received the delivery. For example, point Credit Card Charge at https://yourapp.com/hooks/card-charge and Invoice Paid at https://yourapp.com/hooks/invoice-paid, then handle each route separately.

Event types

These are the events you can subscribe to. Each name is the exact string shown in the dashboard when you add an endpoint.

Transactions

Event	When it fires
`Credit Card Charge`	A card charge completes
`Credit Card Refund`	A card refund is processed
`Credit Card Void`	A card transaction is voided
`Credit Card Chargeback`	A chargeback is filed against a card transaction
`ACH Charge`	An ACH charge is submitted
`ACH Payment Return`	An ACH payment is returned
`ACH Refund`	An ACH refund is processed
`Deposit Sent`	Funds are deposited to the merchant bank account

Recurring payments

Event	When it fires
`Recurring Success`	A scheduled recurring payment succeeds
`Recurring Failed`	A scheduled recurring payment fails
`Recurring Cancelled`	A recurring payment is cancelled
`Recurring Expired`	A recurring payment reaches its end date
`Recurring Paused`	A recurring payment is paused
`Recurring Updated`	A recurring payment is edited

Invoices

Event	When it fires
`Invoice Created`	An invoice is created
`Invoice Updated`	A draft invoice is edited
`Invoice Sent`	An invoice is sent to the customer
`Invoice Paid`	An invoice is paid in full
`Invoice Voided`	An invoice is voided
`Invoice Deleted`	A draft invoice is deleted
`Recurring Invoice Created`	A recurring invoice template is created
`Recurring Invoice Cancelled`	A recurring invoice template is cancelled

Subscriptions

Event	When it fires
`Subscription Created`	A customer is enrolled in a plan
`Subscription Renewed`	A subscription renews for another period
`Subscription Payment Failed`	A subscription renewal payment fails
`Subscription Paused`	A subscription is paused
`Subscription Resumed`	A paused subscription resumes
`Subscription Cancelled`	A subscription is cancelled

Payload format

The request body is a flat JSON object. The event data is sent at the top level — there is no envelope, and no event or type field wrapping it. A transaction webhook:

{
  "transaction_type": "CC",
  "transaction_status": "Success",
  "transaction_status_description": "Approved",
  "transaction_number": "1234567890",
  "transaction_date": "2026-01-01T00:00:00.000000Z",
  "amount": "49.99",
  "customer_uuid": "66f1c230-1337-4g59-b43c-1bcb83adfaaa",
  "transaction_info_id": "9876543210",
  "billing_address": {
    "first_name": "Jane",
    "last_name": "Doe",
    "addr1": "123 Main St",
    "city": "Atlanta",
    "state": "GA",
    "zip": "30301"
  }
}

An invoice webhook:

{
  "id": 4021,
  "invoice_number": "INV-0007",
  "status": "paid",
  "payment_terms": "net_15",
  "issue_date": "2026-07-01",
  "due_date": "2026-07-16",
  "subtotal": 250.0,
  "total": 250.0,
  "amount_paid": 250.0,
  "balance": 0.0,
  "customer": {
    "uuid": "9f2a6c14-3e8b-4d21-9a77-5c1e0b8f4d33",
    "name": "Jane Doe",
    "email": "jane@example.com"
  },
  "items": []
}

Because payloads carry no event discriminator, always identify the event from the endpoint URL that received it (see One endpoint per event above).

Verifying webhook signatures

Dime Payments signs every webhook so you can verify it came from us. The signature is sent in the Signature header as a hex-encoded HMAC-SHA256 of the raw request body, keyed with the secret shown against that endpoint in the dashboard.

$payload   = file_get_contents('php://input');
$signature = $_SERVER['HTTP_SIGNATURE'];
$secret    = 'your-webhook-secret';

$expected = hash_hmac('sha256', $payload, $secret);

if (!hash_equals($expected, $signature)) {
    http_response_code(401);
    exit;
}

Always compare with a timing-safe function such as hash_equals, and sign against the raw body — re-encoding the parsed JSON can reorder keys and change the hash.

Retries

If your endpoint fails to return a 200, Dime Payments retries with exponential backoff. A delivery is attempted up to 3 times before it is abandoned. Because there is no delivery-history screen in the dashboard and no manual retry, treat webhooks as best-effort rather than a guaranteed ledger. Reconcile against the API for anything you cannot afford to miss.

Testing webhooks locally

Use a tool like ngrok to expose your local server to the internet during development:

ngrok http 3000

Use the generated https:// URL as your webhook endpoint in the dashboard.

Next steps

Disputes — understand how chargebacks work
Payouts — understand how funds are deposited
API Reference — full endpoint documentation

Getting Started

SDKs

Going Live

Integrations

Reference

Overview

Setting up a webhook

One endpoint per event

Event types

Transactions

Recurring payments

Invoices

Subscriptions

Payload format

Verifying webhook signatures

Retries

Testing webhooks locally

Next steps

​Overview

​Setting up a webhook

​One endpoint per event

​Event types

​Transactions

​Recurring payments

​Invoices

​Subscriptions

​Payload format

​Verifying webhook signatures

​Retries

​Testing webhooks locally

​Next steps

Overview

Setting up a webhook

One endpoint per event

Event types

Transactions

Recurring payments

Invoices

Subscriptions

Payload format

Verifying webhook signatures

Retries

Testing webhooks locally

Next steps