#prerakthecirqle

1 messages · Page 1 of 1 (latest)

south steppeBOT
last hazel
#

Not necessarily. My customers are created via pricing table -> checkout flow.

So, the subscription and customer creation is not handled by us.

#

The flow I had in my mind was that upon successful checkout, I am listening for the checkout.session.completed webhook, I would be able to add bank transfer for the returned customerId.

torpid lark
#

let me think about it, I'm having a hard time wrapping my head around this. What exactly do you mean by "adding bank transfer" for them? Like they should be able to make that first payment in Checkout using the bank tranfer, or you want to do a one time payment later on and let them do a transfer to pay for it, or you want them to pay their future subscription invoices with transfers, which is it overall?

last hazel
#

They can make their first payment via card using the pricing table checkout process.

For future subscription payments (monthly), I would like to give them the option to pay via bank transfer.

Also, our application generates other non-recurring invoices for them. I would like to give them the option to pay those via bank transfer as well.

#

Does it make sense?

torpid lark
#

it does but unfortunately our docs and the bank transfer product does not make sense

last hazel
#

Yeah, have gone through these docs already.

torpid lark
torpid lark
#

seems that way

last hazel
#

Okay, will give that a try.
While adding the "bank transfer" as a payment method via the dashboard, it calls https://dashboard.stripe.com/v1/customers/cus_LyedEWyWeXfu9Q/funding_instructions with the relevant data.

But I could not find anything like this in the API docs.

torpid lark
south steppeBOT
last hazel
#

I see. I did the following request for a customer, and now I am able to see "bank transfer" as one of their payment methods.

This endpoint is missing from the API docs,so might be a good idea to add it there.

wise dust
#

👋 taking over for my colleague. Let me catch up.

wise dust
#

I'm not sure why we don't actually expose this API in the docs, but I will try to follow up internally about this