Vraag? Stuur ons een bericht

+31 6 26 52 78 57

Wij verwerken online betalingen sinds 2006


Use postbacks to be notified about events that happen in your PayPro account.

Postbacks, also called webhooks, are a way to communicate between the PayPro servers and your servers. Postbacks are simple POST requests that are sent when events occur in your PayPro account. A merchant has the ability to setup postbacks and listen to these events.

Why use postbacks

Most changes in your account happen asynchronously and do not require an API request to trigger. This creates the problem that there is no way for you to know what happens and when.

Postbacks solve this issue by allowing you to register an URL endpoint that will be notified on new events. PayPro will send POST requests, with relevant data for the type of event that occured to the registered endpoint.

These are some example use cases:

  • Sending an email on a completed payment.
  • Sending a product when a new subscription installment has been paid.
  • Update your backend system with status changes.
  • Check when there are chargebacks for direct debits.

User postbacks

If you want to use one single postback URL for your whole account, you can set the postback URL in the PayPro Dashboard settings.

The postback_url parameter in the API call takes precedence over the account settings.

Types of postbacks

There are several types of postbacks you can receive. Each postback type is a different type of event in the PayPro system.


When you create a new payment or subscription there will be a Verkoop postback. This postback contains information about the payment or subscription.


The Termijn postback gets sent when a new installment is created for a payment or subscription. For single payments you will only get one, but for subscriptions you can get several.


When an installment changes its status, a postback will be sent with the type Termijnstatus. You can use this with subscriptions to check if an installment is already paid.


This postback will be sent when you create an invoice.


When a subscription or recurring payment gets paused, you will receive this postback.


When a subscription or recurring payment is resumed, you will receive this postback.


When a subscription or recurring payment is canceled, you will receive this postback.

Handling postbacks

In order to handle postbacks we need an URL endpoint. This can be a simple file on your server or if you use a framework, you probably need to add a new route/controller to setup an endpoint.

The examples below will only show the postback handling code and not the code to create a page.


The postback URL also allows placeholders to be set. These placeholders will contain information about the payment and will be inserted into the URL when the postback is sent.

The following placeholders are allowed for the postback URL:

  • {CUSTOM} Tracker variable or custom field for the merchant. Will be inserted in the affiliate link.
  • {AMOUNT} Amount of the payment, in cents.
  • {AMOUNT_EURO} Amount of the payment, in euro’s. (500 cents becomes 5.00)
  • {AMOUNT_AFFILIATE} Amount of the affiliate commission, in cents.
  • {AMOUNT_AFFILIATE_EURO} Amount of the affiliate commission, in euro’s. (500 cents becomes 5.00)
  • {NET} Net amount added to the merchant’ account. Only available for merchants.
  • {ID} ID of the payment.

Some examples:

  • https://webshop.nl/postback?custom={CUSTOM}
  • https://webshop.nl/postback/{CUSTOM}
  • https://webshop.nl/postback?amount={AMOUNT}&affiliate_amount={AFFILIATE_AMOUNT}


Using the postback_url parameter.

When using these placeholders with the postback_url parameter, you have to make sure that the query parameters are URL encoded. This means the above examples become:

  • https://webshop.nl/postback?custom=%7BCUSTOM%7D
  • https://webshop.nl/postback/%7BCUSTOM%7D
  • https://webshop.nl/postback?amount=%7BAMOUNT%7D&affiliate_amount=%7BAFFILIATE_AMOUNT%7d

API Reference


Would you like additional support or do you have questions? Contact us.