Sagepay Help
- Thread starter suarve
- Start date
Right have been having a little bit of read, am I understanding this correctly (have used Paypal pretty much exclusivly, so Im a bit new to Sagepay at the minute):
Form integration: customer leaves my website to pay on sagepay's payment pages and is then redirected back to my site - all the transaction info is stored by sagepay (cart contents etc.) - nothing like cart contents, billing info are posted back - this is all stored in the sagepay account area and not viewabkle through say my websites admin area.
Server Integration: Like above the customer will be directted to the sagepay pages but it will send a response post to ione of my scripts, allowing me to store all the order information in say a database.
Also, Paypal had a custome hidden field value you could populate with any custom data (E.g voucher code used for example) you liiked. Is this any way to do this using Sagepay? Only way I can see how to achieve this initially is add querystring data onto the notification url. Is there a better way?
Form integration: customer leaves my website to pay on sagepay's payment pages and is then redirected back to my site - all the transaction info is stored by sagepay (cart contents etc.) - nothing like cart contents, billing info are posted back - this is all stored in the sagepay account area and not viewabkle through say my websites admin area.
Server Integration: Like above the customer will be directted to the sagepay pages but it will send a response post to ione of my scripts, allowing me to store all the order information in say a database.
Also, Paypal had a custome hidden field value you could populate with any custom data (E.g voucher code used for example) you liiked. Is this any way to do this using Sagepay? Only way I can see how to achieve this initially is add querystring data onto the notification url. Is there a better way?
Last edited:
With Form it is a good idea to have your cart store cart contents and billing info so you can have a record of what's gone over to the gateway. Form does send back transaction IDs, fraud checking results that should be linked with your records. a lot of the shopping cart's out there normally do this. Form sends a one shot response back to your site and can also send you a confirmation email at the same time.
Server calls your script andwaits for a response to confirm your database knows the transaction succeeded. Again, your database will need to match up the response against the order details that it holds. If Sage Pay don't receive your reply, they will resend the post again and again until you reply.
Sage Pay can handle custom fields as well. Just add those on to your transaction registration post string (&Customfield=I can haz discount plz) when sending over the shopper's name / address / amount etc with the custom field and this will get returned in the notification post.
Server calls your script andwaits for a response to confirm your database knows the transaction succeeded. Again, your database will need to match up the response against the order details that it holds. If Sage Pay don't receive your reply, they will resend the post again and again until you reply.
Sage Pay can handle custom fields as well. Just add those on to your transaction registration post string (&Customfield=I can haz discount plz) when sending over the shopper's name / address / amount etc with the custom field and this will get returned in the notification post.
Apologies for digging up a pretty old thread, have another SagePay question.
I'm currently in the final stages of using Direct on their test system.
I've noticed in the test account screen that there is an option to send HTML email, I've ticked this.
Does the test system send emails, or is that reserved for the LIVE system?
On a side note DIRECT is fairly easy to follow, but I'd personally rewrite the bits that retreieve cart contents as SagePay's method suck imo, very flimsey (E.g. x of y).
Thanky
I'm currently in the final stages of using Direct on their test system.
I've noticed in the test account screen that there is an option to send HTML email, I've ticked this.
Does the test system send emails, or is that reserved for the LIVE system?
On a side note DIRECT is fairly easy to follow, but I'd personally rewrite the bits that retreieve cart contents as SagePay's method suck imo, very flimsey (E.g. x of y).
Thanky
That option won't send any emails with Direct. Sage Pay only send emails when using Form, with Direct you have to generate the emails yourselves.
Yet another question - about 3d secure this time 
I'm just looking at the 3d secure rulebase in my sagepay account. Just spoke to sagepay and they say sometimes it can cause issues with non uk cards.
I'm tempted to setup a couple of rules. E.g. with higher value orders I'll make it so all checks have to be passed, with lower value transactions I'd set it so transactions can go through without 3d secure checks. On all but the higher value transactions, I'd allow the transaction to go through without passing the checks.
Do this sound logical?
Also, I notice there's a tick box called "Allow Authorisations when MPI errors occur" - what exactly is this?
I'm just looking at the 3d secure rulebase in my sagepay account. Just spoke to sagepay and they say sometimes it can cause issues with non uk cards.
I'm tempted to setup a couple of rules. E.g. with higher value orders I'll make it so all checks have to be passed, with lower value transactions I'd set it so transactions can go through without 3d secure checks. On all but the higher value transactions, I'd allow the transaction to go through without passing the checks.
Do this sound logical?
Also, I notice there's a tick box called "Allow Authorisations when MPI errors occur" - what exactly is this?
That's bizarre, as 3dSecure checking comes from the card issuer, so they'd have to be able to get it right otherwise Visa/MasterCard wouldn't sign off the bank using it. AVS CV2 checking is a problem for non-uk cards as some banks only return the security code and don't check the address (Ireland cards are a good example).
With 3d checking Sage Pay sets the checks globally either on or off. High value only with valid 3d checks sounds right, medium value is best allowing 3d and non 3d cards.
For low value payments just don't have a rule. The checks will still take place but you won't filter anything, so no need for a pass, and that way you can still take maesto.
MPI failure is another way to say 'technical problem with the 3d checks'.
Excellent, cheers.
We've had a few situations recently where customers in Germany couldnt pay because the 3d secure wasn't being brought up. Their card wasn't enrolled in the service, but the sign up page wasn't being retrieved either.. which is slightly worrying.
We're strict on our 3d rules, forcing it on everything.
We're strict on our 3d rules, forcing it on everything.
That's really strange, 3d secure isn't meant to be selective in that way. I'd talk to SagePay support.