Events Overview
This page provides detailed information on how Cards Connect uses event notifications to inform you about the transaction outcomes
Card Present Gateway
If you want to access information about our in-store offering, you may check the API specifications here: In-store Transactions Overview
Cards Connect uses event notifications as a second channel to inform you about the outcome of your API requests regarding transactions. Cards Connect notifications are callbacks that contain the response you would receive through a GET API for any of your PUT requests, wrapped with some metadata regarding the respective event notification.
Cards Connect will send notifications for the following outcomes by default
| Operation | Outcomes |
|---|---|
| Authorization | Succeeded Declined Busy Failing Busy Failing Delayed Failed Ruined |
| Capture | Accepted |
| Void | Accepted |
| Refund | Succeeded Declined Busy Failing Busy Failing Delayed Failed Ruined |
| Account Status Inquiry | Succeeded Declined Failed |
Webhook Delivery Assurance
We expect your system to return a 2XX response to mark the notification delivery as successful. If your system fails to handle the webhook notification and returns a 4XX or a 5XX error, automated outcome assurance mechanism will kick-in and retry delivery. Current retry attempt schedule for Cards Connect is:
- Retry immediate re-delivery,
- Retry delivery in 30 seconds,
- Retry delivery in 10 minutes,
- Retry delivery in 1 hour,
- Retry delivery in 2 hours,
- Retry delivery in 1 day.
Updated 2 days ago