Andre

Bug confirmed, thanks @pdbreen for the tip

Hi @CreateSean sounds like a permissions issue? could you please double check your keys? ```java AWS HTTP error: Client error: `PUT https:\/\/torquest-backup.s3.ca-central-1.amazonaws.com\/` resulted in a `403 Forbidden` response:\n\nAccessDeniedAccess DeniedRCZ64S (truncated...)\n...

Hi @incraigulous I was unable to recreate this issue, could you please let me know if you ended up solving this issue?

Hi @mark-chief thanks for reaching out. Could you please confirm where do you expect to see the metadata? if I am not mistaken the metadata should be on the invoice...

Hi @mark-chief Sorry, the metadata will be at the subscription level in Stripe, on your Orders info you can click on the Stripe Reference link and it will redirect to...

Hi @splendidrob please make sure you set the right `testClientId` or `liveClientId` on your config settings. This error may be related to a clientId that is not related to your...

Hi @splendidrob I am looking into this, it looks like Stripe deprecates `express oauth ` I'll let you know when I find a fix in place

Sorry about the slow response, it looks like this needs a big refactor that I just started, just a heads up that this may not be ready until January next...

Hi sorry the slow response here, I will take a look over the weekend, hopefully have a follow up by Monday

Hi @rckywng this ticket it's related to #393 as well. We need to bring support to Stripe API `2023-08-16` as we currently supports [2020-08-27](https://github.com/enupal/stripe/blob/master/CHANGELOG.md#updated-3) This will be a big change...