VivaPayments / API

Index of Viva Wallet open source projects on GitHub.
139 stars 162 forks source link

live transactions not working #1256

Closed GJFox1972 closed 4 years ago

GJFox1972 commented 4 years ago

Ticket ID CC-1226921

Message from my developer

Just completed my investigation and it’s 100% issue from the Viva Payment api they have blocked the the Tokenization request for V1 api so it is something they can help with.

I just did a test transaction and it’s working fine so 100% confirm Viva block the request for live account.

Please send them a mail :- “Live transactions are not working but test are working fine.”

matthewrgourd commented 4 years ago

Hi there, sorry to hear about your ongoing issues. If you could first clarify a few things.

By which method are you attempting to integrate?

Describe the problem as clearly as possible notifying us of any errors generated.

Please provide any request / response logs generated along with screenshots if possible. Blur out any confidential information.

Also, if you could send through any links to previous related issues that may have been closed prematurely I'd be very grateful. Thanks!

GJFox1972 commented 4 years ago

Afternoon Matthew,

We are using the API integration

the integration was tested and it was live

we then changed the domain from a wordpress staging address to the actual address and now its not processing live transactions

Regards Grant Fox 📞 07789882255 Vulpes Media limited T/A Dreambikecompetition™ reg 11794512

GJFox1972 commented 4 years ago

Any news here ?

matthewrgourd commented 4 years ago

Hi there, sorry, still not enough detail about what it is your developer is attempting to do. Is an e-commerce platform for Wordpress involved, e.g. WooCommerce? Maybe get him to reply directly to us via GitHub here...Thanks! To be honest,

Just completed my investigation and it’s 100% issue from the Viva Payment api they have blocked the the Tokenization request for V1 api"

makes no sense at all.

mohitpand commented 4 years ago

Hi there!

When we send the request to this endpoint "https://api.vivapayments.com/acquiring/v1/cards/chargetokens" to Tokenize card according to your API help https://developer.vivawallet.com/api-reference-guide/payment-api/#tag/Cards/paths/~1api~1cards~1chargetokens/post we receive 403 error which means "You are not authorized to access the requested resource." according to you API error code details https://developer.vivawallet.com/api-reference-guide/error-codes/ When I test it with a demo account it's working fine.

Kind regards, Mohit

matthewrgourd commented 4 years ago

Hi @mohitpand the 403 error means there's a problem with authentication. You should be using an OAuth2 bearer token for this? If not, please follow the below instructions before you retry the steps in the tokenization guide:

https://developer.vivawallet.com/authentication/#oauth-2-token-generation

Hope this helps! Let me know how you get on.

Francois-Francois commented 4 years ago

@matthewrgourd I'm concerned too on this issue. Got 403 on same endpoint.

At this point, I use OAuth2 bearer token and the same request with demo credentials are ok.

We've tried to build the auth bearer and credentials 3 times on 3 different person, and it's still the same response.

What can we do ?

matthewrgourd commented 4 years ago

@rikless Are you following the token generation instructions for production when you attempt the switch-over? https://developer.vivawallet.com/authentication/#production-environment

Francois-Francois commented 4 years ago

@matthewrgourd yes

matthewrgourd commented 4 years ago

@rikless please send through any response / request logs so I can check further (blur out any confidential information). If I could also check your account? Email mgourd@vivawallet.com with your merchant ID referring to this GitHub issue. Thanks!

Francois-Francois commented 4 years ago

@matthewrgourd email send !

matthewrgourd commented 4 years ago

Hi @GJFox1972 and @rikless I've spoken to our development team and apparently we've discontinued our Card tokenization API so unfortunately the documentation you've been looking at was incorrect. I've updated the Viva Wallet Developer Portal accordingly. In your calls what you need to do is replace any instances of /acquiring/v1/cards with /nativecheckout/v2 as shown in this information about Native Checkout v2. The production process for card tokenization should then work. Hope this helps!

Francois-Francois commented 4 years ago

mmmh, thank you @matthewrgourd but why does it work on sandbox mod ?

Francois-Francois commented 4 years ago

@matthewrgourd /nativecheckout/v2 endpoint don't allow us to save credit card. What's the issue

matthewrgourd commented 4 years ago

@rikless Ok, didn't realise that. I'll get one of our dev team to look at this tomorrow. They're based in Greece so it's already outside office hours now!

GJFox1972 commented 4 years ago

@mohitpand gutted!

Yann-iBroStudio commented 4 years ago

Hi @matthewrgourd , I'm currently meeting the same issue as @rikless . The ability to save cards with the API is one of the most important features of the project I am finishing. I hope you will find a solution quickly ^^

matthewrgourd commented 4 years ago

Hi @mohitpand, @rikless, @jahazzz, I spoke to our development team and it looks like the ability to save cards is temporarily unavailable. We'll be reintroducing it soon but until then please refer to the Native Checkout v2 page for all the actions that are currently available.

Francois-Francois commented 4 years ago

@matthewrgourd What do you mean by "temporary" ? What is the solution, because we need to save cards.

Vincegypt commented 4 years ago

Hello,

I take over from @rikless to inform you that we are customers at Vivawallet largely for the recurence of payment proposed. We rely on this feature to devellop a new part of our activity. We are therefore looking forward to your return to find out if we need to find another online bank offering recency.

Thank you we are waiting for the reintroduction

Vincent

thefisherbox commented 4 years ago

Hi, We have the same problem, we were developing the same functionality but nom it's impossible. Can You resolve this problem? That's really bad.

Regards, Alexandre

Francois-Francois commented 4 years ago

@matthewrgourd Can you give us more information please ?

Vincegypt commented 4 years ago

Hi everyone, @matthewrgourd if you can give us more concrete information we have spend a lot of money on this and its a big problem for us, please send us some good news.

matthewrgourd commented 4 years ago

Hi all, I'm attempting to find out more info from our dev team. Please bear with me.

matthewrgourd commented 4 years ago

Hi all, the response from our development team is unfortunately they don't know when the functionality will be restored. We know that many of our customers are disappointed so will try our best to get back to you with a solution.

Vincegypt commented 4 years ago

Hi @matthewrgourd , thanks to keep us in touch but we can't accept this answer.... :-)

Please ask them again for a reactivation, we need to finish this project. As i said before we have engaged a lot of money to devellop a plugin with the afirmation from vivawallet that is possible.

We must go forward on this point you have all you need to activate this feature. We can't just wait, some people is working on it we can't stop everything. We wait for good news. :-)

thanks

Vincent

Francois-Francois commented 4 years ago

@matthewrgourd totally agree with @Vincegypt. We can't accept this answer.

Vivawallet confirmed the availability of this feature before we started to work with our dev team.

Your demo API is still live and never thrown this exception so you need to activate this feature. You've been warned one week ago.

Francois

Yann-iBroStudio commented 4 years ago

@matthewrgourd We're talking about professionnal application, business and money ... The least we can expect from a paid service is reactivity and concrete responses with explicit deadlines. This feature works in sandbox so it can't be so complicated to restore it in production.

matthewrgourd commented 4 years ago

I believe we have now also removed it from the sandbox. As I say, we know that many of our customers are disappointed so will try our best to get back to you with a solution.

Francois-Francois commented 4 years ago

@matthewrgourd We're asking for a specific deadline. Time consumed to remove it from sandbox should have been used to make it live again in production. I really don't understand.

Vincegypt commented 4 years ago

Hello @matthewrgourd, Really its not possible, its just a reactivation, i'am sure you can understand our point of view. We have engaged a lot of money because vivawallet is ok with this...

like @rikless i can't undestand, give us a real date, its not a problem to reactivate this fonction. Please continue to ask. Or better give us the direct contact to solve the situation, our position make us more persuasive, its our money in game....

send us some good news...thanks again

matthewrgourd commented 4 years ago

Hi all, sincerest apologies. I've asked the development team again for further info. I'll get back to you if I hear anything.

Francois-Francois commented 4 years ago

@matthewrgourd I don't understand when you say

if I hear anything

Ask your dev team for a response. I think you have to do your best, and can't wait for an optional answer. Handle this issue with your dev team, for real.

matthewrgourd commented 4 years ago

@rikless Sure thing, I am chasing to the best of my abilities!

Vincegypt commented 4 years ago

Really i'am at the same point as @rikless i don't hear a lot of motivation, it's definitly not your money engaged. Please send us a link to discuss directly with the team in charge of the activations. It's not a problem of abilities, its just not an option for us to activate this, our projects just need this to be finished i don't know if you really understand the situation.

Please add the good person to the conversations or link us directly with them.

Thanks again

Vincegypt commented 4 years ago

you can't say something more stressfull than "if i hear something" ....

matthewrgourd commented 4 years ago

@Vincegypt, I've just messaged my colleague and asked him to reply on here saying what's going on.

Vincegypt commented 4 years ago

Hi @matthewrgourd , ok thanks we wait for more informations.

matthewrgourd commented 4 years ago

Hi @Vincegypt, @rikless, @jahazzz, @thefisherbox, @GJFox1972, I've just been informed by our development team that a fix is being worked on for rollout tomorrow. I'll update you again as soon as I have more details.

Francois-Francois commented 4 years ago

@matthewrgourd Thanks for being in touch. Today we are tomorrow. Is that ok ?

Vincegypt commented 4 years ago

Hi everyone, yes @matthewrgourd do you have some good news?

Francois-Francois commented 4 years ago

Hi @matthewrgourd it's now 15 days since you said tomorrow, and we still don't have any news.

Vincegypt commented 4 years ago

Hi everyone, yes @matthewrgourd do you have some good news?

Vincegypt commented 4 years ago

Hi @matthewrgourd please send us some news, we don't have time for holidays here ... :-) we just want to move forward with this point.

thanks

matthewrgourd commented 4 years ago

Hi @rikless, @Vincegypt, I'm finding out for you now (it's my first day back after the Christmas break).

Vincegypt commented 4 years ago

Hi @matthewrgourd thanks

matthewrgourd commented 4 years ago

@rikless @Vincegypt apparently it was a bank holiday in Greece yesterday. I didn't know this as I'm based in the UK. Our development team operates from Athens. Chasing again today...apologies again for the delay.

matthewrgourd commented 4 years ago

@GJFox1972, @mohitpand, @rikless, @jahazzz, @Vincegypt, I'm told the functionality is now available again. In fact, apparently it was restored before Christmas I just didn't have the confirmation. Can you try out and let me know if any further issues? Thanks!

Vincegypt commented 4 years ago

Hi @matthewrgourd thanks for this good news wa are trying right now ;-) we keep in touch

Francois-Francois commented 4 years ago

@matthewrgourd Sorry, but I've tried right now, and this endpoint : https://api.vivapayments.com/acquiring/v1/cards/chargetokens still respond as 403 error when using POST.

And yes, we use OAuth2 bearer token.