account2account failed transactions

[krisMoca]

Hi there,

We've been getting quite a few failed transactions when a customer pays via account2account option.

The system throws typeError when & instead of & is passed back from windcave to the site.

[mylesthedev]

Hi @krisMoca thanks for getting in touch.

This plugin hasn't been tested with the Account2Account feature that Windcave offers. It's likely that there may be additional work required to ensure this plugin and it's dependencies work well with A2A.

Just to help us with investigating a bit more could you please let us know the following:

• current version of Craft Commerce installed
• current version of this plugin installed
• how have you enabled A2A, was this done via Windcave?
• Does this happen consistently on every transaction that is using A2A?

Thank you

[krisMoca]

Hi Myles, Thanks for replying to our issue. * Craft Commerce 3.4.13 * Payment Express 1.5.0 * A2A was done via Windcave by the client. * Yes happened consistently and we were able to replicate the issue - 3 transactions with A2A all failed. Kind Regards, Kris From: Myles ***@***.***> Sent: Tuesday, 9 August 2022 3:01 pm To: PlatoCreative/commerce-payment-express ***@***.***> Cc: Kris Bandong ***@***.***>; Mention ***@***.***> Subject: Re: [PlatoCreative/commerce-payment-express] account2account failed transactions (Issue #5) Hi @krisMoca<https://github.com/krisMoca> thanks for getting in touch. This plugin hasn't been tested with the Account2Account feature that Windcave offers. It's likely that there may be additional work required to ensure this plugin and it's dependencies work well with A2A. Just to help us with investigating a bit more could you please let us know the following: * current version of Craft Commerce installed * current version of this plugin installed * how have you enabled A2A, was this done via Windcave? * Does this happen consistently on every transaction that is using A2A? Thank you — Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUQYWCBQB3Z7U7DULH24DP3VYHCX7ANCNFSM54T5JWJQ>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[mylesthedev]

@krisMoca this can't be resolved within the scope of this plugin. It will actually require an Event hook to be added to Craft Commerce.

This hook would then allow this plugin to tap into the response we get back from Windcave and adjust accordingly.

From what I can see is for some reason the & in the returnUrl is then being encoded to be & but never then decoded.

If we get that event in Craft Commerce I could then apply a fix for this edge case.

You could also Contact Windcave in the meantime to see if it's possible to update their end seeing as PxPay doesn't do this.

[krisMoca]

Hi Myles, Here’s windcave’s response from your last request. ***@***.*** Account2Account is part of Pxpay and if the plugin does not support that then it will be good to update the description of the plugin. Kind Regards, Kris From: Myles ***@***.***> Sent: Tuesday, 9 August 2022 3:53 pm To: PlatoCreative/commerce-payment-express ***@***.***> Cc: Kris Bandong ***@***.***>; Mention ***@***.***> Subject: Re: [PlatoCreative/commerce-payment-express] account2account failed transactions (Issue #5) @krisMoca<https://github.com/krisMoca> this can't be resolved within the scope of this plugin. It will actually require an Event hook to be added to Craft Commerce. This hook would then allow this plugin to tap into the response we get back from Windcave and adjust accordingly. From what I can see is for some reason the & in the returnUrl is then being encoded to be &amp; but never then decoded. If we get that event in Craft Commerce I could then apply a fix for this edge case. You could also Contact Windcave in the meantime to see if it's possible to update their end seeing as PxPay doesn't do this. — Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUQYWCFE2KWV22XN7ZGWZP3VYHIYLANCNFSM54T5JWJQ>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>