Interac auto-deposit email

Blaaiz sends status events when an admin changes a registration to ACTIVE or BLOCKED. Blaaiz also sends an expiry event when a PENDING registration passes its two-calendar-month limit. These events apply to registrations from both the dashboard and the API.

Events and destination

Your business must have API services enabled, a configured webhook URL, and a webhook signing_secret. Blaaiz sends the event to collection_url. If collection_url is null, Blaaiz uses payout_url.

A repeated status does not send another status event. Changes to PENDING or PROCESSING do not send status events. Blaaiz expires only PENDING registrations. The age uses created_at; changes to updated_at do not extend the deadline. The expiry event uses a stable event_id across retries. Use the registration id to distinguish requests that reuse an email. Removal of an ACTIVE registration also sends auto_deposit_email.blocked. After removal, the registration no longer appears in the read endpoints.

Payload

The payload is a flat object. The event name is in type; there is no event field or data wrapper.

{
  "message": "Auto Deposit Email Activated",
  "email": "payments@example.com",
  "status": "ACTIVE",
  "event_id": "01994c21-a4d0-7000-8000-abcdef123456",
  "type": "auto_deposit_email.active"
}

For an expired registration:

{
  "message": "Auto Deposit Email Expired",
  "id": "01994c21-a4d0-7000-8000-123456789abc",
  "email": "payments@example.com",
  "status": "EXPIRED",
  "event_id": "01994c21-a4d0-7000-8000-abcdef987654",
  "type": "auto_deposit_email.expired"
}

For a blocked registration:

{
  "message": "Auto Deposit Email Blocked",
  "email": "payments@example.com",
  "status": "BLOCKED",
  "event_id": "01994c21-a4d0-7000-8000-abcdef654321",
  "type": "auto_deposit_email.blocked"
}

The id field appears only in expiry events. Status events do not include the registration ID, transaction details, or a payment amount. A registration status event does not mean that a customer sent funds. See CAD collection webhooks for payment notifications.

Signature verification

Verify x-blaaiz-signature before you process the payload. Blaaiz signs the timestamp from x-blaaiz-timestamp, followed by a period and the JSON payload, with HMAC-SHA256. Use your webhook signing_secret, not the OAuth client_secret. See Signature verification for examples.

Delivery and status recovery

Activation, blocking, and removal events use synchronous delivery. They do not use the queued webhook log or replay flow. Blaaiz sends expiry events through a queue and retries failed deliveries up to five times. Retry delays are 60, 300, 900, and 900 seconds. A daily recovery run re-queues unprocessed expiry events. These events do not appear in webhook logs or support replay. Return a 2xx response when you accept an event. Store the event_id to avoid duplicate processing in your system.

If you miss an event, read the registration to check its current status. The list endpoint also returns the current status.