---
url: >-
  https://acquirer-api-docs-v4-en.pingpongx.com/en/notes/onlinePayment/recurring/overview/index.md
description: >-
  Recurring is a merchant-initiated stored credential charging capability used
  after cardholder authorization. It is suitable for cardholder-not-present
  scenarios such as auto-renewals and usage-based charges. The merchant decides
  when each charge is triggered and manages the charging plan itself.
---
`Recurring` is an MIT (Merchant-Initiated Transaction) stored credential charging capability used for subsequent merchant-triggered charges after cardholder authorization.

It is not limited to fixed-cycle subscriptions. It can also be used for auto-renewals, pay-per-use billing, and other scenarios where the merchant decides when to trigger the charge.

::: warning
Before going live, coordinate with technical support on the authorization relationship, charge strategy, and retry policy.
:::

## Two Types of Recurring Events

<v4-iImage src = "/v4/recurring/overview.svg" name = "Recurring Event Types"></v4-iImage><br/>

Recurring requires two types of events:
 
+ Cardholder authorization The cardholder confirms card storage and authorizes the merchant to trigger later charges within the agreed scope.

+ Merchant-initiated charge Each subsequent MIT charge is triggered by the merchant and sent through the PingPongCheckout API.

## Execution of Subsequent Charges

The timing, frequency, amount rules, and retry strategy for subsequent charges are all maintained by the merchant side, which then calls the PingPongCheckout API to trigger each charge.

Subsequent MIT charges can take effect only after the first authorization payment succeeds.