![]() |
Quote:
Is intelligence your second language? |
Quote:
I'm not sure that "verifying the information the customer has given" completely covers the overall activities of scrubbing, but maybe I'm misunderstanding your definition. Verification would indicate that you were doing one or more of several checks to verify the validity of the card and the cardholder including:
Obviously Customer information verification can and should check the above and integrate them so that, as an example: AVS is a partial match but the inbound Geo IP is a mismatch, customer is declined. "Scrubbing" would, in my understanding of the definition, include tracking card history, at least internal to CCBill's systems and scoring the transaction based on the history. CCBill's internal systems would then approve/decline based on this score prior to the transaction being submitted to your processor. I.E., Customer A has no historic record in CCBill and passes all "verification" checks and is approved by your internal systems and sent to processor. Customer B has a history with one or more of your Merchants for initiating returns but not in 6 months, passes internal checks. Customer C has charged back a transaction to one or more of your Merchants in the last 6 months, declined, no transaction passed to processor. This pre-authorization internal decision is what can be "tuned" either to make the decision making process more or less restrictive, correct? |
Quote:
|
All times are GMT -7. The time now is 03:59 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc