Close popover
Jerome Recker (Jerome@quavo)
Lead System Architect
Jerome@quavo Member since 2015 27 posts
Posted: June 20, 2017
Last activity: June 20, 2017

On Us Processing for Smart Dispute

Has anyone implemented Smart Dispute for a client that uses both Issuer and Acquirer functionality? How did you handle the OnUsProcessing flow? Out of box, there are only 2 options, Customer Liable and Write Off. My client has a psuedo chargeback process that they follow for On Us claims, that they do outside of the association networks. My first idea to handle this is to create a blended Issuer/Acquirer user type that would work normal Acquirer disputes and the OnUs Issuer disputes. I would then route the Issuer Dispute between these 2 users until the dispute has been resolved. My other idea is to create an acquirer level flow for OnUs, and come up with a way for the Issuer and Acquirer disputes to interact with each other. This solution is probably more complete, but it is also more complicated.

Low-Code App Development
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.