S
Scott Newberry
New to ASP.NET, and really, web programming in general, so please be gentle!
I'm creating a form that allows users their children in an after-school
program. It collects contact info, info on the children, etc. It also
needs to process their credit card payment.
I'm set up with Verisign's PayFlow Link, and posting the data to them and
getting a return is no problem. What I'm left wondering about is how can I
store all of this data only if the payment is successfully processed? What
I was thinking was write the information to a table, along with a unique
identifier, process the credit card, passing the identifier to Verisign as a
user-defined field. Verisign will post back to another page on my site the
results, along with the unique identifier. That ASPX page will go into the
table, mark the record as paid, or delete the record, etc.
Is this a reasonable way of accomplishing this, or is there another
preferred method.
Also, I'm working with Access as a database, or should I just use an XML
file? I'm not familiar with XML, really, but somewhat familiar with Access
and classic ASP. I'd love to use SQL Server, but the non-profit that I'm
trying to do this for isn't going to spend the money to add on SQL Server.
Anyway, the volume of transactions isn't going to be such that there will be
a big performance hitch with Access, I don't think.
Just curious to see if I'm barking up the right tree, or if I'm completely
off-target.
Thanks!
Scott
I'm creating a form that allows users their children in an after-school
program. It collects contact info, info on the children, etc. It also
needs to process their credit card payment.
I'm set up with Verisign's PayFlow Link, and posting the data to them and
getting a return is no problem. What I'm left wondering about is how can I
store all of this data only if the payment is successfully processed? What
I was thinking was write the information to a table, along with a unique
identifier, process the credit card, passing the identifier to Verisign as a
user-defined field. Verisign will post back to another page on my site the
results, along with the unique identifier. That ASPX page will go into the
table, mark the record as paid, or delete the record, etc.
Is this a reasonable way of accomplishing this, or is there another
preferred method.
Also, I'm working with Access as a database, or should I just use an XML
file? I'm not familiar with XML, really, but somewhat familiar with Access
and classic ASP. I'd love to use SQL Server, but the non-profit that I'm
trying to do this for isn't going to spend the money to add on SQL Server.
Anyway, the volume of transactions isn't going to be such that there will be
a big performance hitch with Access, I don't think.
Just curious to see if I'm barking up the right tree, or if I'm completely
off-target.
Thanks!
Scott