![]() |
True cascade billing - who offers it?
A group of webmasters and I were talking in Phoenix about the old fashioned cascade billing where:
if a transaction is declined through one processor, the same transaction is immediately tried through the secondary processor etc example: transaction is declined through ccbill - so ... transaction is immediately and automatically sent through epoch's processing or to a merchant gateway to try for approval From what I understand that is no longer the working model. Now cascade billing means the vendor has to manually switch from one processor to another but NOT use both in combination, is this correct? Are there any sw packages that allow for the old fashioned cascade model hiding out there that I don't know of? |
"true" cascade processing cannot be done with 3rd party processors, you would need your own merchant account.
|
well thats not a problem since I supply the merchant accounts but I was wondering if there are sw solutions inplace for this type of thing?
|
|
Quote:
I was told you can do this through Netbilling and a secondary gateway using MPA. |
Quote:
|
I'm not 100% sure how it works but I think they pass the cc info through a secure socket so he does not have to re-enter it. This can only be done if the merchant is using an API, not a payment form hosted by the billing company.
|
Quote:
|
All times are GMT -7. The time now is 07:06 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123