Quote:
|
Originally Posted by Rice_Master
to my knowledge with using Nats, u can't really have seamless cascading because you can't carry the CC info through another biller... therefore it's pretty much pointless if the visitor have to type out their information again in another form.
|
Hi,
not only with NATS, but with any single software out there. It is impossible to carry the CC info itself from biller A to B unless its a gateway and you control the signup form (in which case NATS does _TRUE_ cascading which is transparent to the surfer, NATS simply posts to gateway A if denied to B without the surfer noticing 2 were even checked).
It has to do with creditcard regulations, NATS is not allowed to know the CC number thus we can not pass it along.
Cascading itself makes sure that surfers do not have to type the same info twice. For example:
You have a join form which asks only for username and password and then lets them choose an option.
The surfer enters those two and chooses the trial option, gets sent to paycom first. Paycom only asks for CC info, the username and pass (which is now not even displayed on the form anymore since the user typed it in before), the country, the zip code and the email address.
The surfer gets declined, NATS now knows the username, password, country, zip code and email address. NATS sends the surfer on to CCBill where those fields are filled in, the others were never asked the surfer by us, so he fills them in.
The surfer gets declined again, NATS now has all address info, username and password and so on, sends the surfer to WTS, the form is completely filled in except for ACH info.
BTW, to my knowledge, NATS is the only system which will allow you to change payment types (CC, ACH, Dialer and so on) during a cascade, at any step. (Someone correct me if I am wrong.)
On top of the basic stuff, your possabilities are endless with NATS. You could for example put a new join form after CCBill in the example above, to let the surfer choose if he wants to try another CC biller, or maybe try a check processor, or a dialer instead.
Of course cascades can be changed based on country of the ip. (At each single step.)
Hope this explains it a bit more,
Fabian