Sagepay - Recurring Billing

03-Feb-2010 09:17 PM

Urban Element

Posts: 32

Hi,

I have a client who has a Sagepay account (UK) and also has a Streamline (Natwest) merchant account. They also have another account with Streamline set up specifically for Recurring Authority Transactions (they needed two seperate as the recurring only excepts certain cards types and with the normal account they can accept a lot more).

He want to sell some products as recurring and some as normal one time transactions. I know BC now supports reuccuring billing which is great and normal one time transactions seperatly but can they both be supported on two different products in the same account as they are both going through one single place i.e. SagePay.

I spoke to Sagepay and they said they support switching between the two merchant accounts as 'all' that needs to happen is a variable to be paseed with the account number (e or c for continous) when the transaction is passed.

I hope this makes sense! My questions was basically is this possible in BC to cope with these two merchant accounts both through the same Sagepay account?

Many Thanks

Malcolm

Malcolm Maclean Creative Director www.urbanelement.com

03-Feb-2010 10:47 PM

Urban Element

Posts: 32

Hi,

If I can be cheeky and tack this one on the end.

I have set up SagePay now to test it out but i keep getting the below response when checking out:

Gateway Response: 4020 : Information received from an Invalid IP address.
Please go back and correct this.

I have added in the Euro and US IP addresses into the allowed list in Sagepay (below) but still no joy and get the same error.

69.20.239.62 for sites on the North American data centre 83.231.190.50 for for sites on the European data centre

Many Thanks

Malcolm

Malcolm Maclean Creative Director www.urbanelement.com

04-Feb-2010 11:32 AM

Support (Admin)

Posts: 2077

Hi Malcolm,

Thanks for the post.

Currently recurring billing for Sagepay is not active, there is a ticket with the development team on this issue. The ticket number is #1633.

Please use the above ticket in future enquiries about this issue.

Although its not certain, this implementation is set to be fixed in our next release in the coming week.

We appreciate your patience Malcolm!

Kind Regards,

Daniel

04-Feb-2010 08:36 PM

Urban Element

Posts: 32

Hi Daniel

Thanks for the reply, should I post here or email directly to the support team to see when this fix is implimented?

Also do you have any idea why i am getting the 'Gateway Response 4020'? I have entered the Euro IP into SagePay but still get the error, am i using the correct IP?

Kind Regards

Malcolm Maclean Creative Director www.urbanelement.com

05-Feb-2010 10:18 AM

Support (Admin)

Posts: 1918

Hi,

The server IPs looks to be correct as noted in the article below.

You may need to follow up with the gateway itself on the reason for the error being thrown.

- http://onlinebusinesswiki.com/index.php/Payment_gateway#Sagepay_.2F_Protx_Payment_Gateway

You can post here if requiring a status on the current recurring fix. Please check back after a couple weeks if the recurring feature still doesn't work.

Kind Regards, Sidney Mitchell

06-Feb-2010 03:18 AM

Urban Element

Posts: 32

Hi

Just thought I would update you. I have now set up a recurring product with my live SagePay account.

When i put an order through it says:
'Token empty or null'

Not sure if this is the error you are fixing or if it is something else.

There is a recurring product on my site http://boundfitness.businesscatalyst.com/ if you want to try it all (0.01p)

If you could let me know when you have an update I will retry the recurring and let you know if there is a change.

Kind Regards

Malcolm

Malcolm Maclean Creative Director www.urbanelement.com

24-Mar-2010 10:26 PM

steve89

Posts: 13

Hi I have the same problem here- BC please test things before you release them!

05-Jun-2010 07:22 AM

Splay

Posts: 47

Hi Guys, I am also having the same problem.

I added North America Servers and European

069.020.239.058 (255.255.255.255) - BC North America
083.231.199.174 (255.255.255.255) - BC Europe

This happens on the nomral shopping cart and recurring payments.

I tried from the businesscatalyst.com and the worldssecuresystems.com domains and its still the same.

ERROR: An error occurred while processing credit card
Gateway Response: 4020 : Information received from an Invalid IP address.

Thanks

17-Jun-2010 02:35 AM

Splay

Posts: 47

Hi Guys,

I finally got the invalid IP address fixed, there are new NA servers and of course new IP's with them.

I am testing the recurring billing option, my understanding is Sagepay suuports this but from the thread I see that BC doesnt, is this the case?

I have put through a test payment and I get the

ERROR: An error occurred while processing credit card
Token was null or empty.

Thanks

17-Jun-2010 03:41 AM

steve89

Posts: 13

Good luck I had to end up using another platform for our recurring customers as BC failed on me so many times.

17-Jun-2010 06:34 AM

Splay

Posts: 47

Oh no, I have put a lot of work into this, it says on the Wiki
http://onlinebusinesswiki.com/index.php/Payment_Gateway#Complete_list_of_currently_supported_payment_gateways
that it is supported.

18-Jun-2010 05:24 AM

Forum Moderator (Admin)

Posts: 2896

Hello,

Typically when a gateway returns that error, it means that it requires a "token" (typically a file) to be present on your website.

This normally is placed in the root directory of your site and may have specific naming conventions to follow. Please contact their support to find out how to get your token.

If their service doesn't require this type of file, be sure you've followed the guidelines in the KB in the recurring billing article and enabled any neccesary features on your gateway. Most of the gateways require setup of an additional feature to work with recurring billing.

Regards,
Justin Price

21-Jun-2010 07:08 PM

Splay

Posts: 47

Thanks for the reply,

I asked Sage Pay in an email about this and this is their response....

"The Invaid Token messege relates to changes in your language code rether than a error messege from Sage Pay.

It maybe worth contacting your software provider regarding the issue as well as asking if they support CA."

It looks like the error is on your side BC.

Thanks

21-Jun-2010 07:32 PM

Urban Element

Posts: 32

Hi

Can someone at BC confirm one way or the other if BC supports Sagepay recurring billing now? Its been haning around for about 6 months, it says in the WIKI it is supported but i think you guys just need to decide one way or the other to save your partners selling the wrong payment gateway to clients.

BC - are you aware of this working on anyone website? Any partners have recurring working with Sagepay?

Kind Regards

Malcolm Maclean Creative Director www.urbanelement.com

21-Jun-2010 08:24 PM

Splay

Posts: 47

I agree.

BC has to understand that their promise of support Sage Pay recurring billing made me convince a client to move from their current provider to Sage Pay.

Based on this promise, I also have spent the last month developing a large content site on the BC platform. I dont want to get to this stage and have to take it all down.

I really love the system and have convinced some more clients to move but this has to be affirmed before doing so.

Thanks

22-Jun-2010 10:09 AM

Forum Moderator (Admin)

Posts: 2896

Hello,

SagePay recurring is supported on the system so there is some issue here most likely.

Can you post the URL of your sites which are using SagePay in their setup so I can run some tests?

Regards,
Justin Price

22-Jun-2010 07:04 PM

Splay

Posts: 47

Hi,

http://simplypainting02.businesscatalyst.com/

The "Insiders" is the recurring billing subscription part

Thanks

24-Jun-2010 12:34 AM

Splay

Posts: 47

Any progress on this?

25-Jun-2010 02:51 AM

Forum Moderator (Admin)

Posts: 2896

Hello Tony,

I've contacted you this morning off the forum as I need some login info. Please check your messages.

Regards,
Justin Price

29-Jun-2010 09:09 PM

Splay

Posts: 47

Justin Hi,

Have done as you suggested in the email but it did not go through.

The suggestion was to change an orders "Recurrance" to daily and enter the card details. I did that yesterday but it did not charge this morning.

This still has not been resolved.

I switched to the live gateway and it was still the same error "Invalid Token".

From what you suggested with setting the recurrance to daily is this what the system does when a recurring payment is processed?
If this is the case then the card details are saved on BC's servers and then presented each iteration for payment to the gateway.

So its a BC service and not a SagePay service. I have been discussing this with SagePay and they have a different understanding of a recurring payment facility.

There is obviously something missing, or a language code issue they mentioned.

Can you please, please, look into this, it is going on weeks now and the client wants to go live this week.

Thanks

06-Jul-2010 07:03 AM

Splay

Posts: 47

I have sent a few mails on this to support and getting no response.

Anybody there?

My client doesn't like to sit in the corner and wait indefinitly.

Thanks

07-Jul-2010 06:23 PM

Splay

Posts: 47

I am getting the message.

Repeated daily emails sent to Justin and no response.

It seems BC want to bury the head in the sand on this one.

Bad show guys.

I have gone out there and sold this to clients, put in hours of dev and now to be let down by the very people I am selling for.

Fact is

BC DOES NOT SUPPORT RECURRING BILLING ON SAGEPAY

Dont waste your time setting it up.

If you need any inside info on it mail me at tony (AT) simplypainting.com

08-Jul-2010 04:02 AM

Forum Moderator (Admin)

Posts: 2896

Hello Tony,

I apologize for not getting back to you, we were shut down for the US holiday here and I was not available for e-mail.

I have e-mailed you further questions if you still wish to pursue this.

Regards,
Justin Price

08-Jul-2010 10:29 PM

Urban Element

Posts: 32

Hi Justin

Thanks for replyign to the thread. I guess we all just want to know if the recurring billing does work in Sagepay or not, so it would be great if whatever is found out in emails or other cases if we could have a definitive response at some point soon it would be really useful for everyone, even if that means it 'does not' work as obviously we are telling our clients it does

Thanks again

Malcolm

Malcolm Maclean Creative Director www.urbanelement.com

08-Jul-2010 11:14 PM

Splay

Posts: 47

Malcolm,

The suggestion in the emails is to set up a product that is recurring and then for the shopper to add that to their cart, checkout and then pay.

This is a workaround and not really feasible in my opinion.

The standard "Subscription Payment" page does not work.

Cheers

13-Jul-2010 11:36 PM

Splay

Posts: 47

Still no resolution on this and emails being ignored.

14-Jul-2010 02:22 PM

Support (Admin)

Posts: 2350

Hi guys,

Thanks for your post.

I've spoken to dev team and I was told this:

"Note: Before being able to do the payment for the recurrent product, you need to log into SagePay, select Direct option, and from “Response to Authorisation POSTs” select “OK/REGISTERED”. Without this setting you'll be getting the “Token was null or empty" message.

Can you please make sure that you have that set?

I'll keep digging further on this with one of the developers that's familiar with that code.

Best wishes,

Mario

14-Jul-2010 07:59 PM

Splay

Posts: 47

I can't find this in my SagePay account so have emailed SagePay support for them to tell me where it is.

14-Jul-2010 11:03 PM

Splay

Posts: 47

The response from SagePay....

****************************************

I would just like to clarify that there is no such setting in the sage pay admin area that was described in the previous e-mail,

The shopping cart provided may have been referring to activating the direct integration method to the account, if you would like me to do so please respond to this e-mail and include the merchant number for the account and I will action your request as soon as possible.

****************************************

Have told them to go ahead, will let you know how it goes.

15-Jul-2010 05:37 AM

Splay

Posts: 47

So,

SagePay emailed me saying it was all set up.

I tried it, and sure what do you expect, NO.

Just to be sure, I emailed SagePay asking if this was also set up on their test servers and their response..

*************************************

Thank you for your e-mail,

I can confirm that Direct integration has also been added to your test account.

If you have any further queries or need any technical assistance, please do not hesitate to contact us.

*************************************

I tested again and not surprisingly, it doesnt work.

I am tiring of the delay tactics guys, is this a test of resolve?

I am a developer and I know this could be fixed quite easily.

If BC have the normal shopping cart checkout going through correctly, then all you gotta do is spot the differences between the one that works and the one that doesnt. It's not rocket science.

My client wants to go live tomorrow, thank you BC for this.

17-Jul-2010 12:08 AM

Splay

Posts: 47

Any news on this yet guys?

20-Jul-2010 12:36 PM

Support (Admin)

Posts: 2350

Hi Splay,

Thanks for your posts.

I have escalated this to the dev team and was told that we have made some changes to the SagePay integration that will hopefully solve this issue or at least return a meaningful message. These changes will be deployed in the next weeks release.

Thank you for your patience!

Best wishes,

Mario

20-Jul-2010 09:03 PM

Splay

Posts: 47

Mario Thanks,

[quote] These changes will be deployed in the next weeks release. [/quote]

Does this mean, this week? Or next week?

Thanks

21-Jul-2010 06:36 AM

Forum Moderator (Admin)

Posts: 2896

Hello,

The update is scheduled for next week, but is subject to change.

Regards,
Justin Price

21-Jul-2010 06:45 PM

Splay

Posts: 47

Not exactly a commited answer and not exactly a promise which can be forwarded to my client.

We are looking at 3 months now on this.

27-Jul-2010 10:00 PM

Splay

Posts: 47

Any news on this guys ??????

27-Jul-2010 10:33 PM

Urban Element

Posts: 32

I think from the most recent Blog Post a fix for this is going to be in tommorows new release. So hopefully one of you guys can cofirm if it works on your sites

Cheers

Malcolm Maclean Creative Director www.urbanelement.com

28-Jul-2010 10:56 PM

Splay

Posts: 47

Any news BC?

30-Jul-2010 10:12 PM

Splay

Posts: 47

Any news BC?

31-Jul-2010 01:09 AM

Splay

Posts: 47

Just tested it and am now getting...

ERROR: An error occurred while processing credit card
Token was null or empty. Gateway Response: 4006 : The TxType requested is not supported on this account.

Before the smoke screen is suggested (I will follow up with SagePay), the original error is still there
"Token was null or empty"

31-Jul-2010 09:03 PM

Splay

Posts: 47

Any news BC?

03-Aug-2010 01:32 PM

Support (Admin)

Posts: 2350

Hi Splay,

Thanks for your posts.

The problem is in your account. Please make sure that you're using live account and not the test account. Also, for the recurring billing to work you need them to enable the following payment action types:

DEFERRED
REFUND
REPEAR

Once you have that setup the recurring billing should work.

Best wishes,

Mario

09-Aug-2010 12:38 PM

Support (Admin)

Posts: 2350

Hi Splay,

Can you please give us an update on this? Did you get it working?

Best wishes,

Mario

13-Aug-2010 11:23 PM

Splay

Posts: 47

Short answer, no, here is what SagePay say about the Recurring Payment option....

The first is to implement the Sage Pay Token system for multiple use. This will allow your site to capture card details or use the Sage Pay payment pages (recommended) to capture the details and issue your site with a token representing the card information. Your site will then have to relate the transaction to the token. This will then allow future payments for the vendor to be processed without the card data being stored on the systems.

In order to use a token, the innitial transaction where the card data is captured will be txtype = TOKEN, this would then generate the token and allow transactions in the future to be passed as Tx type = PAYMENT/DEFERRED/AUTHENTICATE. The type of payment is not restricted with the use of a token, it simply replaces the capture of fresh card data.

Once the token has been issued in order to process a transaction your system would pass the transactional information through to sage Pay along with the token. Our systems would then be able to relate the token to the relevant card details within the database and the transaction would then be able to be processed. A token can be stored for multiple use or for single use, this again would depend on your own requirements.

So, the question is, does BC generate this token and send it along with the transaction details?

Looking at the error that comes back "Token is null or empty", I don't think so guys.

16-Aug-2010 06:09 PM

Support (Admin)

Posts: 2350

Hi Splay,

Thanks for your post.

No. We receive the token from the gateway and store it against the original (master) order. We then use that token in all future transactions.

Best wishes,

Mario

19-Aug-2010 06:52 AM

Splay

Posts: 47

So it looks like SagePay are not sending back a token.

SagePay have given up supporting me and now ignore all mails (is somebody trying to tell me something?)

So I dont know where to turn, utterly disappointed.
Thinking of pulling the whole thing down and building from scratch on my own servers.

19-Aug-2010 07:04 AM

Splay

Posts: 47

I tried something different last night.

I created a product "Insiders Subscribe" and on the form you just buy this.

The order goes through OK .

I go to the order in the admin and I set it to recurr, I set it to daily, the next billing date is tomorrow, tomorrow comes, guess what, the bloody thigh doesnt work.

I put through a different order. Same thing, set the recurrance to daily, wait another day, doesnt work.

Guys, I have given this months. I am really let down and just have to move on. So close but falling at the very last stage.

It's such an awful pity. I thought once Adobe took over they would be looking to gain customers not loose em.

24-Aug-2010 07:19 PM

Splay

Posts: 47

Sage Pay got back to me with this....

If they are getting TOKEN is null or empty in the TOKEN field can you make sure they are passing the TXTYPE of TOKEN upon authorisation - I can only suggest we are not generating it based on this or we are and it is not being stored by them.

What do you think guys, are you sending the TXTYPE ??