#mike-j_api
regal fableBOT
👋 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/1407348133276680224
📝 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.
- mike-j_api, 5 hours ago, 9 messages
- mike-j_api, 3 days ago, 28 messages
covert gyro
hi there!
I get an error that apple_pay and google_pay don't support on_behalf_of, and it dies.
can you share the request ID (req_xxx)? you can find it here https://dashboard.stripe.com/test/logs
regal fableBOT
agile sedge
I assume that when a booking is going through without me first trying to remove Klarna, the Stripe system recognises that those two cards are unsuitable and ignores them, but I don't have the information to do the same
covert gyro
apple_pay and google_pay are not valid payment method.
if you accept card payment method, then Apple/Google Pay will automatically be enabled.
so remove apple_pay and google_pay from your API call.
agile sedge
All I'm doing is grabbing the payment method configurations, grabbing those that say available=true, and pass them back. It makes me feel like I'm doing something wrong if I have to start applying too much stripe business logic in our backend, if you see what I mean? That pmconfig api call says they are all available. How am I to know they aren't all available?
I don't really want to be hard coding "remove apple/google pay" because what happens when we add another with the same issue?
Should I be using something else to get the payment options we've turned on?
storm fable
Hey taking over for @covert gyro as they had to step away.
agile sedge
Hi, no problem. Unless I'm mistaken, this may be an extension of a conversation you and I were having yesterday
storm fable
Taking a step back, what it looks like you're trying to achieve is two different scenarios. Your intuition is correct, your current approach is not the optimal way to solve this.
Instead of trying to read and override the individual payment method types, you can set up two distinct payment method configurations for your scenarios. One could be for pay in full, the other could be for any other cases which would exclude Klarna. You can create these payment method configurations ahead of time in the dashboard or using the API. Then when you create a payment intent, you can specify which payment configuration to use.
This would allow Stripe to automatically configure everything that's compatible, and always exclude Klarna according to your business logic
agile sedge
Ahhhh, I had a thought about what a specific configuration would be/do, and forgot to chase it up. So where abouts in the dashboard can I find the option to set that up?
Found it - Payment methods
So when configuring a payment intent or a setup intent in our backend, I can specify there which payment configuration to use?
Yeah, found that in the api docs. OK, I'll give that approach a whirl - sounds more hopeful 🙂
Thanks
storm fable
No problem, let me know if you have more questions!