Man
Professional
- Messages
- 3,029
- Reaction score
- 553
- Points
- 113
1. 0-Auth
2. Pre-Auth
3. Purchase (or Purchase + Void)
4. Telephone Banking
0-Auth - is what it sounds like. Many mobile applications use this method for confirmation a card is valid when customer adds a new method of payment. It's worth noting that this is not a requirement and not all services choose to check valid, and just use luhn verification instead. Not all merchants are afforded this function as well. Mobile App examples using 0-auth include Sunoco, Grubhub. Merchants services from processors providing 0-auth include Authorize.net, for example. People can feel free to expand on this, should they wish.
Pre-Auth - is standard procedure that runs a preliminary charge on the payment device as sort of a "soft-hold". That is, merchants have the ability to confirm that the funds are available and thus preventing the risk of the charge declining which otherwise might elevate their risk level assigned by the processor/gateway. If risk is qualified above acceptable levels the merchant may have the cost per transaction, and % of each transaction increased and/or have their account privileges terminated. Pre-authorization is also useful for customers since if the transaction is not completed, or is less than the authorization amount, they will typically be reimbursed much quicker than it would take to refund them. Again, much like 0-auth, not all merchants have the option to perform pre-authorization and largely applies to certain business models. Companies in this category include pay-at-the-pump gas stations, and hotels and motels. If we are not in control of the business account, using pre-auth for checking valid is essentially no different than completing a purchase. Merchant service providers that allow pre-auth by default include Chase Paymentech.
Purchase checking - is probably the most common way to confirm if a card is valid. Popular services like try2check can be used for this or you can use a private merchant with API or virtual terminal to submit a sale and wait for approval or decline. Most options will provide the option to void a sale, but depending on the issuers internal control and risk alert procedures, this may or may not be advisable. Additional research is suggested for best results according to your workflow.
Phone checking - involves call the support number that is printed on the back of the card. Each bank will have different requirements, but it's almost always better to call in from the owners phone. Some may require ssn or pin, and may have adverse affects if not supplied correctly.
Addition to virtual terminal: most merchants have the ability to pre-authorize, check, or purchase through the processors phone system, too. Mercury is the best, in my opinion.
2. Pre-Auth
3. Purchase (or Purchase + Void)
4. Telephone Banking
0-Auth - is what it sounds like. Many mobile applications use this method for confirmation a card is valid when customer adds a new method of payment. It's worth noting that this is not a requirement and not all services choose to check valid, and just use luhn verification instead. Not all merchants are afforded this function as well. Mobile App examples using 0-auth include Sunoco, Grubhub. Merchants services from processors providing 0-auth include Authorize.net, for example. People can feel free to expand on this, should they wish.
Pre-Auth - is standard procedure that runs a preliminary charge on the payment device as sort of a "soft-hold". That is, merchants have the ability to confirm that the funds are available and thus preventing the risk of the charge declining which otherwise might elevate their risk level assigned by the processor/gateway. If risk is qualified above acceptable levels the merchant may have the cost per transaction, and % of each transaction increased and/or have their account privileges terminated. Pre-authorization is also useful for customers since if the transaction is not completed, or is less than the authorization amount, they will typically be reimbursed much quicker than it would take to refund them. Again, much like 0-auth, not all merchants have the option to perform pre-authorization and largely applies to certain business models. Companies in this category include pay-at-the-pump gas stations, and hotels and motels. If we are not in control of the business account, using pre-auth for checking valid is essentially no different than completing a purchase. Merchant service providers that allow pre-auth by default include Chase Paymentech.
Purchase checking - is probably the most common way to confirm if a card is valid. Popular services like try2check can be used for this or you can use a private merchant with API or virtual terminal to submit a sale and wait for approval or decline. Most options will provide the option to void a sale, but depending on the issuers internal control and risk alert procedures, this may or may not be advisable. Additional research is suggested for best results according to your workflow.
Phone checking - involves call the support number that is printed on the back of the card. Each bank will have different requirements, but it's almost always better to call in from the owners phone. Some may require ssn or pin, and may have adverse affects if not supplied correctly.
Addition to virtual terminal: most merchants have the ability to pre-authorize, check, or purchase through the processors phone system, too. Mercury is the best, in my opinion.
