I am currently in the process of creating a custom payment provider for Sage Pay and all is working well until Sage Pay is trying to call the notification url after entering card details.
I have created the notification url in the following format:
<hostname via ngrok>/umbraco/vendr/payment/callback/sagepay-payment-provider/6537c4ec-0af8-4ea2-ac18-b945cadd1fec
but if I try to hit that endpoint from my computer it just gives me a 400 bad request, and Sage Pay also does not like it.
Can I ask, is this the correct way of hitting the callback for a custom payment provider, I have checked the alias is "sagepay-payment-provider" and that the id of the payment provider is also correct.
Would be great to get some additional testing feedback. You can raise issues on the provider github repo or feel free to submit any PR's for anything you think isn't quite right.
Ahh that is perfect, saves me a bit of time!! I will get it installed over the next couple of days and let you know how I get on with it, and obvs will raise any issues or just sort via PR if I spot any.
Just a quick note to say the SagePay payment provider has worked perfectly for me so far, had it up and running and processing test transactions within a couple of minutes of installing and setting it up.
As you might be aware, SagePay have annoyingly re-branded recently so given this provider hasn't officially been released yet we are looking to rename to Opayo so that it is inline with the rebrand.
I just wanted to check though, has you project gone live yet? I don't want to make it difficult for you to upgrade if it already has. Although saying that, it should really just be updating a value in the database to point to the new payment provider alias.
Let me know if this would be a pain for you or not.
Apologies for the late reply, been on holiday for a couple of weeks :) no problem with the name change, the project hasn't gone live yet so I can just perform the upgrade if the package has now been changed, is it on the same repo?
We've released an official 1.0.0 so this will be available from the NuGet gallery. I've actually got some code in there that points a previous setup to the new setup so it should work with your project already, but if you wanted to move it over, it would mean updating in the database the payment methods payment provider alias to be "opayo" instead of "sagepay".
I just wanted to check though, has you project gone live yet? I don't want to make it difficult for you to upgrade if it already has. Although saying that, it should really just be updating a value in the database to point to the new payment provider alias.
Custom Payment Provider - SagePay
Hey Matt,
I am currently in the process of creating a custom payment provider for Sage Pay and all is working well until Sage Pay is trying to call the notification url after entering card details.
I have created the notification url in the following format:
but if I try to hit that endpoint from my computer it just gives me a 400 bad request, and Sage Pay also does not like it.
Can I ask, is this the correct way of hitting the callback for a custom payment provider, I have checked the alias is "sagepay-payment-provider" and that the id of the payment provider is also correct.
Any help/insight would be appreciated.
Thanks,
Graham
Hey Graham
If you can hold on a little we are hoping to get a SagePay provider released this week.
Nik Rimington has been working on one and he has kindly contributed it back to us. We just need to get it packaged up and released.
Matt
Ok, here we go.
We've now got the source code at https://github.com/vendrhub/vendr-payment-provider-sagepay and will be looking to release it soon.
In the mean time, you can trial it out via our unstable nuget feed at https://nuget.outfield.digital/unstable/vendr/v3/index.json
Would be great to get some additional testing feedback. You can raise issues on the provider github repo or feel free to submit any PR's for anything you think isn't quite right.
/Matt
Ahh that is perfect, saves me a bit of time!! I will get it installed over the next couple of days and let you know how I get on with it, and obvs will raise any issues or just sort via PR if I spot any.
Graham
Thanks Graham,
Hoping to get some docs sorted soon, but hopefully it makes enough sense for you to figure it out, but just ask if not.
/Matt
Hey Matt,
Just a quick note to say the SagePay payment provider has worked perfectly for me so far, had it up and running and processing test transactions within a couple of minutes of installing and setting it up.
Cheers,
Graham
Hi Graham,
As you might be aware, SagePay have annoyingly re-branded recently so given this provider hasn't officially been released yet we are looking to rename to Opayo so that it is inline with the rebrand.
I just wanted to check though, has you project gone live yet? I don't want to make it difficult for you to upgrade if it already has. Although saying that, it should really just be updating a value in the database to point to the new payment provider alias.
Let me know if this would be a pain for you or not.
Matt
Hey Matt,
Apologies for the late reply, been on holiday for a couple of weeks :) no problem with the name change, the project hasn't gone live yet so I can just perform the upgrade if the package has now been changed, is it on the same repo?
Graham
Hey Graham,
No worries. Hope you had a pleasant holiday.
We've released an official 1.0.0 so this will be available from the NuGet gallery. I've actually got some code in there that points a previous setup to the new setup so it should work with your project already, but if you wanted to move it over, it would mean updating in the database the payment methods payment provider alias to be "opayo" instead of "sagepay".
Hope this helps
Matt
I just wanted to check though, has you project gone live yet? I don't want to make it difficult for you to upgrade if it already has. Although saying that, it should really just be updating a value in the database to point to the new payment provider alias.
watch movies hellodear.in
is working on a reply...