Page MenuHomePhabricator

Declines due to API settings
Closed, ResolvedPublic

Description

Greetings FRTech,

I detected a new sort of decline in our decline mix recently and made an inquiry with Ingenico about them. The decline is 'scenario not successful' (see below) which is new to me. After pushing Ingenico about this, they suggest that there is an issue with our recurring API call.

From Ingenico: Wiki is sending isRecurring=1 instead of isRecurring=true. Also I'm confused why it is being sent in cardPaymentMethodSpecificInput instead of hostedCheckoutSpecificInput. It seems like if they want to use recurring so they also need to submit endDate and minFrequency to be able to perform 3Dv2. Maybe it would be good to have some technical person from Wiki to contact me to go over their API calls.

Can someone from FRTech be available to have this call with myself and Ingenico to explore this topic and hopefully favorably impact these declines?

image.png (728×351 px, 48 KB)

Event Timeline

Wiki is sending isRecurring=1 instead of isRecurring=true. Also I'm confused why it is being sent in cardPaymentMethodSpecificInput instead of hostedCheckoutSpecificInput. It seems like if they want to use recurring so they also need to submit endDate and minFrequency to be able to perform 3Dv2. Maybe it would be good to have some technical person from Wiki to contact me to go over their API calls.

We'd be happy to get some input from them! In the meantime, we could clarify whether they're talking about the initial setup (where we use a hosted checkout and where we DO put the isRecurring flag under the hostedCheckoutSpecificInput) or a subsequent installment (where we use the base create payment API call that has no hostedCheckoutSpecificInput) . We can certainly switch isRecurring to use true and false instead of 1 and 0 if their platform now requires it.

//From Ingenico: The logs I received from my team were not very clear so I couldn’t distinguish if you are submitting the “hosted checkout” API or the “create payment” API.

So based on your teams comments it looks like the subsequent installment (create payment API) is correct, indeed the only change required for this is to change isRecurring 1 and 0 to true and false and everything else is OK.

For the initial setup (hosted checkout API) I have not received any logs from my team, so hopefully your team can provide an example of this call. This is the API call that requires the 3D fields so we should focus our efforts on getting this API call right.//

Change 734358 had a related patch set uploaded (by Damilare Adedoyin; author: Damilare Adedoyin):

[mediawiki/extensions/DonationInterface@master] Set isRecurring value to boolean instead of numbers

https://gerrit.wikimedia.org/r/734358

Please let me know if you would like to have a call with Ingenico to discuss the API 3D fields correct.

Change 734358 merged by jenkins-bot:

[mediawiki/extensions/DonationInterface@master] Set isRecurring value to boolean instead of numbers

https://gerrit.wikimedia.org/r/734358

@Ejegg, could I kindly get a copy of the API call to have Ingenico review so I can close this out with them?

XenoRyet set Final Story Points to 1.