How is the Structure of Notify (Webhook) in the REST API?

The Notify (Webhook) in the REST API significantly differs from the Blowfish interface, especially in terms of data transmission and retrieval.

Differences from the Blowfish System:

  • Blowfish: The Blowfish interface included all transaction data in the notification.
  • REST API: The REST API only sends the generated PayID in the webhook.

Processing the Notification:

  • Webhook Call: The webhook is sent as a POST request, for example with the body {"PayID":"b1de0f447c664d8898ef61aa6815b785"}.
  • Content-Type: The content type is "application/x-www-form-urlencoded; charset=iso-8859-1".
  • Security Aspects: The IP range of the Paygate is provided upon request to ensure the authenticity of the requests.

Retrieving Additional Information:

  • Transaction Query Endpoint: Merchants can use the /payments/{paymentId} endpoint to determine the status and the TransID (merchant reference) based on the PayID.

Summary

The Notify (Webhook) in the REST API offers a secure and structured approach, where merchants receive the PayID and must query additional transaction details through a specific endpoint. This represents a shift in the processing of payment transactions and requires merchants to accordingly adjust their systems and processes.

Was this article helpful?
0 out of 0 found this helpful