Thank you for the post. Could you please provide some business scenario examples of what you mean by continuous payment authority use case? Much appreciated. 

1. Both Visa and MasterCard allow chargebacks on “recurring transactions” processed using a credit or debit card, which SD can process OOTB. There are conditions involved for a successful chargeback – in general, the cardholder must have withdrawn permission, and the merchant and/or Acquirer (merchant’s bank) must have received a notification of the cancellation, and one of the card associations recommends that the Card Issuer provide copies of that request.

   
   

    

2. At present, SD does NOT have a “stop payment” or “cancellation” process OOTB where a card is involved, as doing this does not necessarily mean the customer needs to file a dispute.  If the customer has our Customer Service app, this could possibly start as a “service case” from which a dispute in SD could be launched.  We are including the service messages for building out the communication to VROL for “stop payments”, but the workflow for that would have to be extended in the field.

   
   

    

3. For the US, there is a “block merchant” process for ACH, but, again, this does not translate for “card”. 

Hi,

Thanks for the reply. For now we will deep dive into what is required and understand if we need custom build to address this in SD framework. 

Milind