Subscriptions via tokenization (API)

Payrexx provides the capability to receive recurring payments through tokenization via the API.

The abbreviation "API" stands for Application Programming Interface. It refers to a set of commands, functions, and protocols that allows software to interact with another system.

Tokenization involves storing a payment method for future payments. You can learn about the benefits of tokenization and how to set it up in Payrexx in the following article:

Tokenization

Technical Information

Technical information and instructions for enabling subscription payments through tokenization can be found in the relevant article in our developer documentation:

Tokenization | Developerdocs.payrexx.com

Frequently Asked Questions

In which cases are the webhooks "Transaction" and "Subscription" triggered for subscriptions?

• Cancellation: The "Subscription" webhook (status: cancelled) is triggered.

• Updating a payment method: The "Subscription" webhook with the new token data is triggered.

• Charge: The "Transaction" webhook is always triggered. If the charge is successful, the "Subscription" webhook is additionally triggered with the updated billing date (next_pay_date).

Is it possible to cancel a subscription at the next expiration date via the API?

No, the API only supports the immediate deletion of a subscription (DELETE). Cancellation effective at the end of the billing period can only be configured in the Payrexx merchant administration, not via the API.

Is it possible to update a customer’s address data via the API?

No, address data is tied to the payment process and cannot be updated independently via the API.

When does Payrexx send confirmation emails?

If the sending of confirmation emails is enabled under Settings > Notifications, Payrexx will send the emails. If the setting is disabled, Payrexx will not send any emails.