#mattcomroe_api

1 messages · Page 1 of 1 (latest)

cloud palmBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1370385954787037307

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

summer edge
#

Hey there, talking a look at these examples

vague quartz
#

thank you! i appreciate your help.

summer edge
#

The payment_method approach is the updated pattern, but the problem is not that parameter but the mandate you sent

#

mandate: "mandate_1RKtjsBnxMPxdETuvzAwvgSH",

vague quartz
#

yes; that was a single-use mandate that had expired.

#

so i need to request a new one with the next payment_intent create request.

summer edge
vague quartz
#

but the source parameter is now deprecated, right? i think that's part of the issue; we didn't use to have to include the mandate string in our PaymentIntent create call.

summer edge
#

You either need to supply new mandate_data with the subsequent payment (similar shape to the original payment) after collecting that from your customer
or
with the first payment & mandate collection, you use setup_future_usage to establish a multi-use mandate you can supply later like you tried to do.

vague quartz
#

i have an updated pattern that i'm pushing today which should fall more in line with that. added the setup_future_usage param to the PaymentIntent create call and passing the appropriate new mandate_data along with it

summer edge
#

So for example if you'd specified setup_future_usage: 'off_session' in the first request, then the second request with the mandate parameter would likely have worked

summer edge
vague quartz
#

ok great. that is what i'm doing going forward.

#

but source is out. i should just remove that, right? nothing can use that source parameter again?

#

or is it deprecated but still working for now?

summer edge
#

Correct, thats effectively deprecated. Any legacy sources that only work with source have been hard deprecated there already. The only ones remaining functional there currently (bank account and cards) also work as payment_method

vague quartz
#

ok.. i think i've got what i need for now. thank you again for your help. i appreciate you!

summer edge
#

No problem, happy to help! And come back if you hit any issues with that 🙂