Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Acquirer & Reseller

Reference


This section provides reference information for platform implementation and operation, with links to additional technical documentation.

Frequently Asked Questions

This section provides FAQs about Recurring Billing.

Can I reapply a token management template after enabling a merchant for Recurring Billing?

No. The merchant can overwrite the configuration with their own settings as needed. If a template is reapplied, it overwrites the changes that the merchant has made.

How are merchants invoiced for Recurring Billing transactions?

Billing details depend on the contract terms that the reseller has with the Visa Acceptance Solution.

Is the solution available on network token?

Yes. Recurring Billing is available on both and network token.

Will merchants receive any notifications?

Yes. Merchants manually set up notifications using webhooks. sends email notifications to their customers.

What retry logic does Recurring Billing use for failed payments?

See System Retry Logic in the Recurring Billing Developer and User Guide.

Can the schedule of retries be customized?

No. Retry schedules are not customizable.

Does Recurring Billing work on Secure Acceptance?

No. Recurring Billing does not work with Secure Acceptance. Instead, merchants follow these steps:

  1. Integrate to to collect the payment instrument.
  2. Integrate to to create the customer token from the transient token.
  3. Integrate to the new Recurring Billing service that uses the REST API.
  4. Become familiar with the new Recurring Billing service user interface in .
Can a plan be created for a subscription that has a trial period of a certain number of days before the billing start date?

No. Currently, subscriptions do not support a trial period in which a different amount is charged initially and then changed.

However, a merchant can create a subscription with a payment start date relatively far in the future, such as a week or a month. Between the subscription creation date and the first payment date, the subscription remains in the pending state. A setup fee can be charged for the first transaction.

Is it possible for a merchant to pause a customer's subscription?

Yes. Subscriptions can be suspended and then reactivated using both the REST API and .

Does use of the Recurring Billing REST API automatically comply with merchant-initiated transactions (MIT) and credentials on file (COF) transactions requirements?

For REST API use cases, the merchant must ensure compliance by setting up customer initiated transactions (CIT) as described in Customer-Initiated Transactions with Credentials on File in the Payments Developer Guide.

For use, described in the Merchant Boarding User Guide, compliance is managed by the system.

What is meant by "the merchant needs to provide MIT fields during authorization?" The Recurring Billing engine handles recurring sale transactions, so merchants do not actually trigger authorization.

While the Recurring Billing engine handles recurring sale transactions, the responsibility for MIT compliance varies depending on the method of transaction initiation:

  • For subscriptions created using the REST API, the merchant is responsible for ensuring compliance with MIT requirements.
  • For subscriptions created in , the system manages compliance, including for all future transactions based on the initial payment. Merchants must authorize the new payment instrument with all subscription-related fields and provide the network transaction ID during subscription creation.
Is there an option for a variable amount, like a Mastercard Standing Order transaction?

No. Currently Recurring Billing does not support variable amounts or standing orders.

Is Recurring Billing a relevant option for telco merchants?

Telco merchants bill different recurring payment amounts each month for individual customers. Currently, Recurring Billing does not support variable amounts or standing orders.

Are webhooks relevant to Recurring Billing?

This table lists webhook event notifications for Recurring Billing transaction results:

Product IDEvent TypeNotification Type
recurringBillingrbs.subscriptions.charge.failedRecurring payment failed
recurringBillingrbs.subscriptions.charge.pre-notifiedRecurring payment is upcoming
recurringBillingrbs.subscriptions.charge.createdRecurring payment succeeded

For details, see Create Webhook Security Keys in the API Explorer: POST /kms/egress/v2/keys-sym

What is the sale transaction time for Recurring Billing? Is it still 3:00 a.m. PT, or is it customizable?

Sale transactions for Recurring Billing are charged after 2:00 a.m. in the merchant time zone. The transaction time is not customizable.

How to Get Help

Acquirers distributing products have access to the Visa Acceptance Solutions Support Center for these resources:

  • Knowledge base articles, frequently asked questions, and supplemental documentation for platform and products
  • Support request submission system
  • Account-specific support resources

Contacting Client Services

For Client Services contact information, refer to the Support Center knowledge article How to Contact Client Services.

Developer information is available at the Visa Acceptance Solutions Developer Center.

Additional acquirer documentation is available from the Documentation Hub.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.