#nj0y-Customer

1 messages · Page 1 of 1 (latest)

undone nymph
#

Hi, sorry for the inconvenience, but I think our API doesn't support that way (The List Customer API does require type)

#

👋 @grave pier let's continue here

#

Normally you wouldn't need to list all payment methods with a Customer. What would you want to achieve with it?

grave pier
#

I want users to be able to set up payment methods for future billing with Stripe Checkout. So I thought I could use Stripe to set them up. Then depending on their monthly invoice I would charge using their preferred payment method.

#

Similar to how Google charges for their API usage.

#

So my website accesses Stripe to list all they payment methods tied to the customer account. But I am told I can't do this without iterating each and every method type separately.

undone nymph
#

When you used Checkout, which mode did you use? There are "payment" "setup" and "subscription"

#

I think Subscription?

grave pier
#

setup

#

Subscription I assumed is for fixed recurring amounts.

#

So, at the break of a new month. My website cooks all invoices, calls stripe and tries to make sense which method to use for charging.

#

Appearantly Stripe was not designed for this. And I am amazed how this strategy would be so unconventional that I can't really use it.

undone nymph
#

Hmm

#

How about just using Stripe Subscription mode with Checkout?

#

What prevent you to do that and make you need to cooks all invoices from your side?

sand pond
#

@grave pier would not the customer's preferred payment method be the one they setup on your platform? Perhaps that;s the confuision - customers do not have "generic" paymentMethods accross platforms - they have paymentMethods they setup with YOUR plATFORM

grave pier
#

I think I can make use of default_payment_method for this. I am gonna need it if there are more than one methods present.

undone nymph
#

When you finish the Checkout Session in setup mode, you can listen to webhook and set the default_payment_method, yes

grave pier
#

But let's say I wanna fallback to a secondary payment. Then I seem to have to iterate exactly each and every type to collect what's actually attached.

undone nymph
#

Do you predict that your customer could go to Checkout and setup multiple times?

#

Each time a Setup is done, let's save the payment method id, or its type to your database

#

when you cooks your Invoice, take it from your database based on your Customer Id

grave pier
#

I am predicting they could add a sepa_debit and a fallback to card. but depending on the region there may be more methods that can be used. Like iDeal for NL, sofort for Germany etc.

#

let's save the payment method id, or its type to your database when you cooks your Invoice,
Yeah I was hoping I could rely on Stripe being the master for all that.

undone nymph
#

I am stepping down for the day. If you have additional questions feel free to open a new thread!

smoky echoBOT
#

This thread has been archived. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact