Preauthorized Payment Cancellation Service Documentation

Ready to start coding?

Things to Know

The Preauthorized Payment Cancellation Service (PPCS) enables Visa consumer credit, debit, and commercial card issuers to stop preauthorized electronic funds transfer payments (including recurring and installment payments) from being authorized, cleared, and settled through VisaNet. The service provides issuers with a method for handling cardholder stop payment requests.

It is important for the cardholder to understand that using the Preauthorized Payment Cancellation Service (PPCS) API does not release them of the responsibility to pay the merchant for services as per their agreement with the merchant. 

For further information, contact


The following table lists the regional availability for Preauthorized Payment Cancellation Service. To view availability of all products, refer to the Availability Matrix.

Available in entire region

Limited availability in region

Not available

Product Name Availability Notes
Preauthorized Payment Cancellation Service
Product Name Availability Notes
Preauthorized Payment Cancellation Service
Product Name Availability Notes
Preauthorized Payment Cancellation Service
Product Name Availability Notes
Preauthorized Payment Cancellation Service
Product Name Availability Notes
Preauthorized Payment Cancellation Service

Getting Started

Through this service, issuers can place stop payment orders in the VisaNet Cardholder Database (CDB) on behalf of their cardholders, which effectively informs acquirers and their merchants, via an authorization response code, that a cardholder has requested a stop payment. When a matching stop payment order is in place, VisaNet will decline the transaction to the acquirer on behalf of the issuer during authorization. If the transaction is submitted for clearing and settlement, VisaNet will return the transaction to the acquirer.

The process for stopping a recurring payment transaction is as follows:

  1. The issuer places a stop payment order in the Visa cardholder database using a file maintenance message.
    1. The message is submitted using the issuer’s or issuer processor’s own application, which in turn submits the request to Visa through this API.
    2. The message contains the Visa card/account number, the stop payment reason; it may contain optional information such as merchant name, Card Acceptor ID, Merchant Verification Value, and transaction dollar amount.
  2. VisaNet matches authorization and clearing messages based on:
    1. Transactions identified as recurring or installment payments.
    2. Matching criteria defined in the stop payment order by the issuer.
  3. If a match is identified, VisaNet:
    1. Declines an authorization request with a descriptive response code.
    2. Returns a clearing message to the acquirer with a descriptive return/reclassification reason code.
    3. Sends an advice to the issuer with a descriptive reason code.

How Does It Work?

Stop Payment Orders

Enables Visa debit card, credit, and commercial issuers to submit stop payment orders and revocation of authorization orders to VisaNet.

Decline Authorizations

Permits VisaNet to decline an authorization request to the acquirer on behalf of the issuer with a descriptive response code when a stop payment order or revocation of authorization order is on file with VisaNet.

Automatically Return Clearing Transactions

Permits VisaNet to automatically return a clearing transaction to the acquirer on behalf of the issuer with a descriptive return reason code when a stop payment order or revocation of authorization order is on file with VisaNet.

Descriptive Advice

Gives issuers descriptive advice whenever an authorization is declined or a clearing transaction is returned.

Issuers can integrate their call center, back office, mobile or online banking systems to the PPCS API to give their staff or their cardholders the ability to cancel a preauthorized payment for a given merchant after the cardholder has contacted that merchant.

Why Use It?

Offers a Wealth of Benefits to Issuers

  • May help enable US Visa debit card issuers to meet their regulatory requirements when consumers contact their issuer to stop preauthorized payments from their accounts after contacting the merchant.
  • Can reduce the need for issuers to charge back preauthorized payments because the stop payment orders and revocation of authorization orders are on file.
  • May improve the cardholder experience of using bill pay and subscription billing services.
  • Can reduce automatic bill payment operational costs.
  • Can help to reduce authorization declines for preauthorized payments.

Benefits Acquirers, Too

  • Provides acquirers and their merchants with descriptive authorization response codes and return reason codes.
  • Helps reduce chargebacks and authorization declines by providing information that a stop order is on file.
  • Encourages consistent handling of stop payment orders and revocation of authorization orders.

Gives Cardholders Convenience and Control

Preauthorized Payment Cancellation Service gives cardholders a way to stop payment of preauthorized funds transfers from their accounts after they have notified the merchant—facilitating more control and convenience. Visa provides an integrated solution within an issuer's back-office or call center application to allow them to initiate stop payment requests.

Keeps Merchants Informed While Reducing Chargebacks

Preauthorized Payment Cancellation Service lets merchants know that a consumer has stopped payment or revoked authorization of a preauthorized funds transfer. This communication enables consistent handling of stop orders, which may reduce chargebacks for preauthorized payments.

APIs Included

Stop Payment Order API

Enables an issuer to stop a specific preauthorized payment to one merchant, all future preauthorized payments to one merchant, or all preauthorized payments for multiple merchants (for closed accounts), on behalf of the cardholder.

Stop Payment Details API

Enables an issuer to get details of a stop payment order identified by ID or case number.

Stop Payment Inquiry API

Provides details of all stop payment orders identified by a cardholder account number.

Visa Transaction Controls

Using the Stop Payment Order API

The Stop Payment Order API allows you to place a stop payment order in the Cardholder Database. There are three types of stop payment orders. The first is a basic stop payment order, which stops a specific payment for a given cardholder account number to a specific merchant one time. The second is a revocation of authorization order, which stops all payments for a given cardholder account number to a specific merchant for all time as long as the stop payment order is active. The third type, used for closed accounts, is a revocation of all authorization orders, which cancels all recurring and installment payments for a specific account for any merchant.

Types of Preauthorized Payment Cancellation

    Stop Payment Order Types and Response/Return Codes

Stop Payment Order Type
Response Code for Declined Authorization Messages
Return/Reclassification Reason Code for Clearing Transactions
R0—Stop Payment Order (Stop a specific payment.)
R0 C0
R1—Revocation of Authorization Order (Revoke authorization for further payments to a specific merchant.)
R1 C1
R3—Revocation of All Authorization Orders (Cancel all recurring and installment payments for a specific account. Used for closed accounts.)
R3 C2

Required Information

Required information in PPCS Stop Payment requests are:

  • Card/Account Number
  • PPCS Stop Order Type
  • Merchant Information
  • Acquirer Country Code
  • Payment Information

Using the Stop Payment Details API

The Stop Payment Details API allows you to get details of a stop payment order, including cancellation type, card acceptor ID, merchant name and expiration date. Searching by stop payment order ID or case number retrieves details for that specific order.

Using the Stop Payment Inquiry API

The Stop Payment Inquiry API allows you to get details of all stop payment orders on file for a given cardholder account number. Send the account number in the request and receive the same details you receive from the Stop Payment Details API in the response. You can decide whether you want your project to display all details or one or more key details.

Security and Authentication Requirements

The PPCS APIs use mutual SSL authentication and channel encryption, which will require the issuer to obtain a user ID and password as well as to install a PKI certificate issued by Visa. You can receive the test credentials from the Project Dashboard for sandbox testing. Production credentials will be supplied to you as part of the production on-boarding process. Contact for more information or to begin the production on-boarding process.

Service Activation Requirements

Activation and testing is required for participation in PPCS. Issuers and their development partners must schedule testing and certification through their Account Manager. Issuers must complete the following documentation to request activation of PPCS for an issuer- or issuer processor-developed system.

  • Client Information Questionnaire—Each issuer BIN to be enrolled in PPCS must be included on the questionnaire to be activated in the V.I.P. Customer Online Repository (CORE). (The form is available from VOL, your regional Visa CSS Representative, or Account Manager.)
  • Visa Resolve Online Enrollment Form—Requests enrollment in and appropriate permissions for Visa Resolve Online (VROL) and PPCS. The form is available from VOL, your regional Visa CSS Representative, or Account Manager.)

For further information, contact

Best Practices and Tips for Using PPCS

The PPCS API simulator can be used by any developer in the sandbox. Currently, however, only issuers and their partner service providers can use the PPCS APIs in production.

PPCS API is cross-interface compatible with host-based V.I.P. messages and Visa Resolve Online (VROL) User Interface (UI) and Real-Time Systems Interface (RTSI) messages. If you have multiple organizations and departments using PPCS through different interfaces, the stop orders will be compatible across interfaces. This means that you can add through one interface, update through another interface, view through another interface, and see all adds and updates on one report.

There are two ways to implement your project to prevent creation of duplicate stop payment orders: 

  1. Do an inquiry to check if an order already exists. If an order already exists that covers the type of stop payment you need, then do not send a new order. 
  2. Use the XML element “DuplicatePPCSInd” set to “true”. This will inform the PPCS system to check for an existing identical stop payment order and prevent a duplicate from being created if one already exists. 

Issuer clients with access to Visa Online can view the PPCS Quick Reference Guide, which contains the following information for making the best use of PPCS:

  • “Preauthorized Payment Cancellation Service Best Practices” provides suggestions to enable issuers to begin using PPCS quickly. There are also best practices suggestions that can help issuers make effective use of the service.
  • “Sample Preauthorized Payment Cancellation Service Scripts” provides suggested scripts for issuer CSRs to use for calls from Visa cardholders regarding stop payments for preauthorized payment (recurring and installment payment) transactions.