Postbacks-Webhooks are simply notifications our system sends to your given postback_url(defined by you when creating payments, payouts, authorizations, registrations, checkouts) for updates on transaction statuses.
Postbacks and Webhooks are the same thing, and this naming be used interchangeably. We suggest to whitelist and accept notifications from our approved IP addresses.
Note: Only HTTPS addresses with TLS 1.2/1.3 will be accepted as postback urls.
Postbacks can contain extra information based on a payment method, however, all of them will contain at least:
| Parameter | Value |
|---|---|
| transaction_id | Unique ID of the transaction. |
| payment_type | Payment type of the transactions. Find more about payment types here https://docs.c-payment.de/reference/list-of-payment-methods. |
| status_code | Integer status code of the transaction's status. Find more about statuses here https://docs.c-payment.de/reference/list-of-transaction-statuses . |
| status | String status name of the transaction's status. Find more about statuses here https://docs.c-payment.de/reference/list-of-transaction-statuses. |
| order_id | Order ID of the transaction. |
| message | Additional information about transaction's status or response. |
| additional_transaction_data | Optional string field which merchants can save and retrieve additional data from a transaction. This parameter is available to be passed in our transaction creation endpoints. |
| checksum | Checksum of the the postback message. We suggest to use IP validation to verify the authenticity of the messages. However if you like to use checksum verification, follow our guide in this link. |