Legacy recurring payments

PayNowPro payment intents support legacy recurring-payment fields. For new recurring billing integrations, use the Subscriptions API, which models the customer, product, recurring price, active subscription, billing history, and plan changes as separate records.

Legacy recurring fields

A legacy recurring payment is created through a payment-intent request with intentType: 'RECURRING'. The request can include:

• frequency: Daily, Weekly, Fortnightly, Monthly, BiMonthly, Quarterly, or Yearly.
• period: An optional billing-period value.
• executionDate: An optional scheduled execution date.
• initialPaymentAmount: An optional initial amount.
• customerId: An optional existing PayNowPro customer ID.

The stored payment intent may include the next execution date, current period, recurring status, and recurring transaction number.

When to use subscriptions instead

Choose subscriptions for new recurring offers when you need to:

• Link a recurring price to a catalog product.
• Manage active subscriptions by customer.
• Retrieve billing history.
• Track plan changes as upgrades or downgrades.
• Cancel a subscription through the subscription API.

Read Create and manage subscriptions to build a new recurring-billing flow. Use the Payment intent API reference only when you need to maintain a legacy recurring integration.