[SOLVED] Sage Pay

Hi there, I am planning on using Sage Pay (in UK) as the payment method on my site (oc version 1.4.9.3). I have noticed that Sage Pay is one of the payments options shipped with OC. Reading about Sage Pay integration (on sage pay site)I understand that there are different Sage Pay integration options: Form, Server, Server & inFrame and Direct. Could somebody clarify which option is used by OC Sage Pay module? Is there any post explaining/detailing OC Sage Pay? Thanks in advance.

You can use any of those options you list.

I have just set up this on a new client store, i used 1.4.93 like you, i used sagepay direct module from the backend, this means that the user never leaves your sitevand details are input there(use ssl), the other sagepay module if used will take the user off your site and use a secure sagepay page which you can custmoise your logo.

I strongly advise you to try sagepay simulator, just put in a few details after clicking the link below and sage will just create a sanbox sage account for you, just input the details into the sagepay module (cant remeber if simulator works with sagepay direct) and go through a payment process using dummy details they give you or i think you can make them up yourself.

Heres the link to sign up for a simulator sagepay account, think it expires after 24 hours, i wish somone had told me about this when i was the same questions as you.

https://support.sagepay.com/apply/Reque ... count.aspx

Hope this helps.

Chris

hi webpie it,
you have been really helpful. Thank you very much.
all the best.

No problem buddy.

Regards
Webpie iT.

Hi.
I have been testing Sage Pay Direct with "Simulator" (thank you for your advice) and came across something which i don't know if its right. I was wondering if you or anybody else had similar experience.

Basically I placed a test order and proceed to pay, when click Confirm Order i get a message telling me that the transaction had failed. I then realized it was a typing error, Mt instead of Mr. made the amendment and click confirm order again, this time the transaction failed because: [The VendorTxCode '17' has been used before. Each transaction you send should have a unique VendorTxCode.] After looking into the php code i see that the value for VendorTxCode equals order_id. Does it means that if customer makes a mistake he/she cannot rectify it straight away an continue??? or I am missing something? Has anybody encounter this situation and if so, any idea of how o handle it elegantly?? Please!

Thank in advance.

Hi Huron

Glad you found the simulator etc...

Does it means that if customer makes a mistake he/she cannot rectify it straight away an continue??? or I am missing something?

I have not come across this problem to be honest, if something mistyped for me, an error regarding the misspelling or card rejected will show and then that gives me a chance then to re-edit that info, then resubmit the order.

I do believe though that it does appear in sage as two orders, one that is failed and one that has success.

Personally if you want a really answer though, I would get Q, and and draw his attention to your post, as he could give you a factual straight up answer.

Sorry my answer is not s detailed.

Webpie iT.

Thank you.

Sorry my answer is not s detailed.

Your answer is very much appreciated!

I will see if i can replicate the error and see exactly what happens. I wonder if there is a setting within Simulator to accept repeated VendorTxCode.

Hopefully is something simple!!

Cheers.

To note i did only use the simulator once, then the sage account for my client was setup, and they provide a test account, so maybe it is something specific to the simulator, i did mess around with the settings in the simulator but as i said, only used it once and then went on to the test account the the live account, which worked how you would expect it to

Webpie iT.

I think I now know what occurred.

On the Sage Pay Simulator, Main Menu / Direct…

The setting for “Response to Authorisation POSTs” was set a Random. (If everything is formatted correctly and is validated successfully the system will send either an OK/REGISTERED (60% of the time), NOTAUTHED (25%), REJECTED (10%) or ERROR (5%) to Simulate Live transactions.)

So, the transaction 17 was registered because it passed , but an ERROR response was sent back for testing the code’s handling of the issue… when I try to re-submit then it really failed because transaction 17 was already registered. In reality if the first transaction really fails it would not have been registered at all. which means transaction 17 would only register once when successful so client does not need to amend anything.

OC was ok.

Hopefully all of the above makes sense, and might help somebody in the future if in similar situation.

Huron

Cool man glad you resolved that and thanks for posting and explanation, i found sage support on here near to nothing, not because people ignore it, just because people use the free checkout solutions or their own ones.

So glad we have added to the Sage support.

Chris

Hi Chris
Waiting now to set the merchant account and have some test on the real "Sage Pay" server. fingers crossed all will go well.
Let hope more people start using sage pay direct and have more support.
Very glad i came across OC.
All the best.
Huron