-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recurring Payments Not Processing Correctly with WooCommerce #99
Comments
Hi Eiman, Thank you for reporting this issue. We will figure this out for you. Are you able to send me the entire log file? You can email it to [email protected] Kind regards, |
Hi MarcusSure. I’m assuming that you want the woo log?There’s a screenshot attached of the logBest Regards \ Med venlig hilsen Eiman MarzoukEmail: ***@***.*** 21 Oct 2024, at 17.21, Marcus ***@***.***> wrote:
Hi Eiman,
Thank you for reporting this issue.
We will figure this out for you.
Are you able to send me the entire log file? You can email it to ***@***.***
Kind regards,
Marcus Dahl
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi, I need the log from the WooCommerce -> Status -> Logs -> Vipps MobilePay Recurring Payments area. Try initiating a payment and triggering the error before sending me the log, though. Or send the log from the day you tried this last 😄 Unfortunately it looks like attachments are not automatically included when you reply to this issue via email. GitHub does not automatically attach the file. Try emailing it to me manually at [email protected] instead 😄 |

Med venlig hilsen / Kind regards
Eiman Marzouk
Telefon: 20 62 78 73
E-mail: ***@***.***
… On 21 Oct 2024, at 17.58, Marcus ***@***.***> wrote:
Hi,
I need the log from the WooCommerce -> Status -> Logs -> Vipps MobilePay Recurring Payments area.
Try initiating a payment and triggering the error before sending me the log, though. Or send the log from the day you tried this last 😄
Unfortunately it looks like attachments are not automatically included when you reply to this issue via email. GitHub does not automatically attach the file.
Try emailing it to me manually at ***@***.*** ***@***.***> instead 😄
—
Reply to this email directly, view it on GitHub <#99 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIZGCBMILU6IPMOCYSD6ITZ4UQDZAVCNFSM6AAAAABQERV652VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGA4DSNBVHE>.
You are receiving this because you authored the thread.
|
I need a moment to set up the recurring payment again. I changed it so users wouldn't get an error message.
I'll set up everything again initiate a payment and send a fresh log to you
Med venlig hilsen / Kind regards
Eiman Marzouk
Telefon: 20 62 78 73
E-mail: ***@***.***
… On 21 Oct 2024, at 17.39, Eiman Marzouk ***@***.***> wrote:
Hi Marcus
Sure. I’m assuming that you want the woo log?
There’s a screenshot attached of the log
<212873221–13629.png>
Best Regards \ Med venlig hilsen
Eiman Marzouk
Email: ***@***.***
On 21 Oct 2024, at 17.21, Marcus ***@***.***> wrote:
Hi Eiman,
Thank you for reporting this issue.
We will figure this out for you.
Are you able to send me the entire log file? You can email it to ***@***.*** ***@***.***>
Kind regards,
Marcus Dahl
—
Reply to this email directly, view it on GitHub <#99 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIZGCGW5GS5Z7HD7FDZN2DZ4ULWTAVCNFSM6AAAAABQERV652VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWHE4TIMZVHA>.
You are receiving this because you authored the thread.
|
I’m encountering an issue with the WooCommerce recurring payments integration using the Vipps Recurring API. When users attempt to subscribe, they successfully log in, and I can confirm that the recurring payment method is being sent in the payload. However, I receive a 400 HTTP error with the following message:
The payment method used is not supported. PaymentMethod must be one of 'wallet', 'card', 'recurring'.
Steps to Reproduce:
Additional Information:
Expected Behavior:
Screenshots & Logs:
The text was updated successfully, but these errors were encountered: