Skip to main content

Recurring Payments

Recurring payments imply the generation of a token. Tokens are payment solutions that secure the customer's payment details behind a token ID. Once you create it, you can charge your customer for subsequent purchases without requesting them to provide their payment details again. There are two types of token payment:

Customer-Initiated​

A single, isolated payment performed with a token.

Merchant-Initiated (or Recurrences)​

Payments with a given periodicity, like subscriptions.

warning

Revup does not manage recurring payments automatically.

  • Our system does not keep track of the periodicity or amount of recurring payments.
  • It is the merchant's responsibility to periodically request Revup to perform a new transaction according to the characteristics of the service charged to the customer.

Key Differences: Recurring vs Single Payments​

  1. The initial payment requires the creation of an order in which the merchant specifies it is an initial payment and also enables a flag to request the generation of a token.

  2. The customer and their credit card details are present for the first payment. Revup processes them in form as usual, and it will return a token ID in the callback to redirectUrl.

  3. The merchant triggers the recurring payments. There are no credit card details or payment forms involved. Whenever they want to charge the customer, the merchant must create an order indicating that it is a recurring one.

  4. The recurring payment will go through by sending a request to the Revup API from now on. This request must include the token ID generated previously and also the transaction ID of the initial recurrence (a.k.a. parent ID transaction).

  5. The last payment in a series of recurrences must specify in the order that it is a final one. Once an initial recurrence is associated with a final recurrence, the token will be disabled.