#ton-emendis-bv_api

1 messages ¡ Page 1 of 1 (latest)

robust ridgeBOT
#

👋 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/1326179813014376521

📝 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.

static hill
fading spoke
#

Okay so instead of implementing both setupIntent endpoint en payment method endpoint for my customer I can just implement setupintent?

static hill
#

I'm not sure I would think of it in terms of endpoints and raw API calls, I would think of it in terms of the full-stack payments integration. But for instance there is payment_method_data as a parameter on the SetupIntent API to create a PaymentMethod in-line, and that's what our frontend libraries are using.

fading spoke
#

I don't see that on the setupintent object

image.png
static hill
fading spoke
#

But what does it look like in the SetupIntent Object? is it like this?

"payment_method_data": {
"sepa_debit": {
"iban": NL44ABNA0984413186,
}
},
"payment_method_types": [
"sepa_debit"
],

#

payment_method_data*

static hill
#

something like that yes. to be clear you don't need to know the exact format since in general you'd follow the guides and our frontend makes the requests for you, but if there's more context on what you're doing I can try to help/elaborate