The Triple Play Pay Webhooks
Webhooks offer a powerful method for web services to communicate in real-time, enabling one application to send automated updates or information to another application immediately after an event occurs.
This technology empowers developers, system integrators, and business process automators to create more responsive, efficient, and interactive systems by leveraging event-driven architecture.
At Triple Play Pay, we champion the use of webhooks to enhance inter-application communication, ensuring that our products and services remain at the cutting edge of technology.
Generic Webhook Body
Note this is simply an example to illustrate the potential response bodies.
Enrollment Webhook Body
The first webhook you will receive from us will be `APPLICATION_SUBMITTED`. It signifies that we've gotten the application successfully.
The second webhook you receive from us will be a notification you've gotten credentials to our sandbox api. You will be able to take the "message" attribute from the event body and use it in upstream requests to talk to the application, like so:
Authorization: Bearer --YOUR_TOKEN_GOES_HERE--
The third webhook represents the fact that the underlying application is now in the underwriting stage of our process.
The next webhook is one Triple Play Pay sets on our end when we need to pause the procedure to address a range of issues which may happen with the application. This status is a hold one, and you will be informed of it via the webhook below.
If we have to terminate the application for any reason, as opposed to the hold status above, we will emit this decline message in our webhooks.
This next status indicates that production credentials have been generated for the account on hand. This will allow you to call our production APIs.
The final status you'll receive in this domain is this one. It will come generally paired up with the production credentials.
Transaction Webhook
Get informed exactly when every transaction takes place, both for your own and your child merchant entities.