exxos's Atari, Amiga & retro forum

derkom wrote: ↑Fri Aug 30, 2019 4:23 pm Oh, the Sagepay docs say to zero-pad the IP (for some reason). Have you tried putting 081.004.101.012 in the Sage control panel?

Edit: Subnet mask apparently also needs to be zero-padded (although if you're allowing from only one IP, this'll be 255.255.255.255 regardless).

It does it automatically..

Drat. Thought I had stumbled onto the problem. I notice you've got 255.255.255.000 as the subnet mask there. No reason that shouldn't work, but that will (theoretically, if things were actually working) open up access to a bunch of other customers at your VPS provider. You should have 255.255.255.255 in there if you've got only one IP. You still might try fixing that and giving it another go....

I had 255 in the first time, it didn't work, so I deleted it and put in 000. There isn't anything else I can really put in

I think Sage is like most other companies, bad support, bad docs, broken system. Even when/if I get this working with my proper test account, it still doesn't mean it will solve my original problem with the sandbox account either

EDIT:
I even tried putting in my own IP address as well at one point.

exxos wrote: ↑Fri Aug 30, 2019 4:34 pm...bad support, bad docs, broken system.

Yep, looks that way. Maybe time to throw the ball back in their court. But as you say, even if it's fixed, it may be one step forward, two steps back...

I gave in and rang them up..

They said there is normally a 24H wait for IP's to be added to the account.. they just did it for me (the account only got setup a few hours ago).. So now there is new IP in there...

While they on the phone I tested the 3D-secure bit and..

{"status":"Authenticated"}

{"statusCode":"0000","statusDetail":"The Authorisation was Successful.","transactionId":"70D9FBC6-E725-E8C0-7CB3-5242A825E7C2","transactionType":"Payment","retrievalReference":2272544,"bankResponseCode":"00","bankAuthorisationCode":"999777","paymentMethod":{"card":{"cardType":"Visa","lastFourDigits":"0006","expiryDate":"0123","cardIdentifier":"E1AEF6E3-0AAA-44F4-BBEA-AAB94157AA7A","reusable":false}},"amount":{"totalAmount":10000,"saleAmount":10000,"surchargeAmount":0},"currency":"GBP","fiRecipient":{},"status":"Ok","avsCvcCheck":{"status":"SecurityCodeMatchOnly","address":"NotMatched","postalCode":"NotMatched","securityCode":"Matched"},"3DSecure":{"status":"Authenticated"}}

So now 3DS seems to be working

It seems that the sandbox account doesn't work with 3DS then

Would be nice if they would put a notification right on the admin screen telling users about the waiting period.

derkom wrote: ↑Fri Aug 30, 2019 4:54 pm Would be nice if they would put a notification right on the admin screen telling users about the waiting period.

Indeed, that be to easy I mean foolish me assumed once the account was setup, it was ready to use

exxos wrote: ↑Fri Aug 30, 2019 4:14 pm Get the same IP...

Can confirm, this is the IP that connects with my server and uploads the backups.

I've been working on the flow of the payment system. Normally the 3D secure boxes appear on sites in a frame, or basically on the checkout page. I tried that, but it kinda looked silly on a otherwise blank page. Plus with it being a Iframe, responses went to the frame, so I had to break out of the frame to continue the checkout.

In the need I just removed then frame . its a bit rubbish to just have the small 3D box on its own page, but that is issued from the bank, so I have no control over it anyway. It makes things a lot easier in not squashing it in a frame just to break out of the frame afterwards.

I've also since found there is V1 3DS which sites are using now anyway. Then there's V2 which is the one EU screwed up for us all. V2 isn't even out of beta testing yet and the deadline is only days away now. There are some docs how to setup V2 and I will look into that next week.

It seems unclear how it will pan out. Some credit companies said they are not moving to V2, but then elsewhere says its mandatory in 2020. Sage says they will fallback to V1 if V2 isn't supported by the card issuer.

As for me. I will try and setup V2 as best I can now. Then hopefully it won't cause headaches down the line.

As a side note, I know items are going out of stock in my store again in terms of RAM and PSUs etc unfortunately with me having to spend 100% of my free time on the store code, I have had no time to work on stock or any other projects for the matter. With my day work getting busy I'm struggling to free up time for the coding as it is. So I'm going to be backlogged for a while with everything

More fun. Worldpay have signed me up for a business account, which according to Sage I don't need and have to cancel it It's a good job I am keeping a eye on all this as per-usual companies sign you up for stuff you never asked for in the first place .

EDIT:

Ok rangup worldpay, what a faff. Seems the business dashboard is £4.99 a month which sounds like a "bolt on" to the account. The "lite" version of the dashboard only goes back 14 days with order history by the sounds of it. At no point was I given any options or was this even explained