Boarding Webhooks
Boarding webhooks notify you about merchant onboarding status changes and specific boarding process events.
Merchant Status Events
The following webhooks are triggered when a merchant’s status changes during the boarding process:
merchant.new
Triggered when merchant status changes to “New”.
merchant.sent_for_signature
Triggered when merchant status changes to “Sent For Signature”.
merchant.signed
Triggered when merchant status changes to “Signed”.
merchant.in_underwriting
Triggered when merchant status changes to “In Underwriting”.
merchant.boarded
Triggered when merchant status changes to “Boarded”.
merchant.live
Triggered when merchant status changes to “Live”.
merchant.cancelled
Triggered when merchant status changes to “Cancelled”.
merchant.declined
Triggered when merchant status changes to “Declined”.
merchant.unknown
Triggered when merchant status changes to “Unknown”.
VAR Complete Event
boarding.varcomplete
Triggered when boarding VAR (Visa Account Range) process is complete.
Integration Tips
- Status Tracking: Maintain merchant status in your system based on webhook events
- Automated Communications: Send status updates and next steps to merchants automatically
- Team Notifications: Alert sales and support teams about status changes
- Credential Management: Securely store and distribute gateway credentials after activation
- VAR Completion: Update merchant records when VAR completion occurs
Error Handling
Handle potential issues in boarding webhooks:
- Missing Data: Some optional fields may be null depending on application completeness
- Status Transitions: Ensure your system can handle status changes in any order
- Duplicate Events: Use idempotency keys to prevent duplicate processing
- Failed Activations: Handle cases where activation may be reversed due to compliance issues