Callbacks
The Request to Pay via QR Code API supports callbacks to notify your application of real-time status updates when an event occurs. Callbacks are more efficient for both the API provider and clients because applications don’t need to frequently poll for data to get status updates.
Before you begin
To enable callbacks, you will need to:
- Contact your J.P. Morgan Representative to initiate an implementation request when you are ready to start using the J.P. Morgan Treasury Services API.
- Complete the implementation process to receive the certificate necessary to set up a new callback. For more information, see Getting Started.
How callbacks work
When a payment request is received, it is acknowledged with a successful 201 HTTP status that includes a unique transaction id and payment details in the response body. During the lifecycle of a payment request, clients recieve a callback during each status change according to their preferences and configuration.
The payment initiation status webhook response is typically received within 30 seconds. The Request to Pay API is designed to provide timely and accurate information about the payment. If an HTTP error occurs, J.P. Morgan automatically retries until the error is no longer received.
Status response types
The following table lists supported status response types by the Request to Pay API.
| Value | Description |
|---|---|
ACTIVE |
Payment Request captured but not settled |
PROCESSING |
Payment is being processed |
SETTLED |
Payment Request captured and payment settled |
EXPIRED |
Payment Request expired |
CANCELLED |
Payment Request cancelled |
Next steps
Learn how to test using mock data to trigger specific responses and error scenarios.