#rhoxio

1 messages · Page 1 of 1 (latest)

scarlet krakenBOT
oblique cedar
#

You can't use the bank account provided during connect onboarding as a payment source - you can only use it for payouts

#

Only bank accounts that are created as PaymentMethods or Sources can be used for payment

wary jewel
#

Ok. So my options are limited to the payment options provided by Connect in this situation?

oblique cedar
#

I'm not sure what you mean by that?

#

To clarify - the payment methods you can choose from for payment and the external accounts you can set up during onboarding are completely separate

scarlet krakenBOT
wary jewel
#

When I visit the payment link generated by the Stripe Checkout Session, it provides me with card or other available options I turned on in the dashboard. That's what I meant by the 'payment options provided by connect' piece.

Right, I understand the difference between the two now. It seems odd to me that you can't initiate direct transfers with this, as the site advertises the functionality to be similar to Uber and Lyft. I understand that these are generally one-off payments, but it confused me for sure.

In order to get this working as I intended (payout from bank account to bank account directly), I would need to use Stripe.js to create the bank account, set the Source on the applicable customer then essentially go from there with PaymentIntent and Transfers/Payouts?

rotund pasture
#

hello! taking over from karbi, gimme a few minutes to get caught up

wary jewel
#

No problem! Thanks.

rotund pasture
#

you can still use Checkout to collect the payment method details (and save it for future use on the Customer if you don't want to charge it now). Subsequently, use PaymentIntents and Transfers/Payouts

wary jewel
#

Alright. The webhooks don't seem to be giving me back a customer object, though. It does give me back payment methods, though.

When retrieving the payment method using the API, the customer comes back empty. Does this mean that I can just set/create the Customer directly and save their payment method that way?

I'm really trying to avoid having to use BCES Debit if possible for AUS transactions. Can I pass the customer into the CheckoutSession and have the bank account be the primary option if they set the bank account (as a Source) up beforehand? The docs only mention card data, but I assume any valid Source (a bank account in this case) would work.

rotund pasture
#

if you're trying to avoid using BECS debit, would you prefer to simply omit it as a payment method option for your customers?

wary jewel
#

Ok, thank you for the info! This has been super helpful.

My actual goal is to set it up so users can pay other users for a service. It's not so much as omitting the option (I can handle the mandate stuff for BECS) but I want to ultimately use Stripe for direct bank-to-bank transfers. Is this possible to do for Australian bank accounts? My research tells me that BCES is more-or-less the Stripe default for these types of transactions. The main problem with this is that the BECS default limit is low, and this would be for payroll type of transactions over $1000 in some cases. I know that I can request the limit be raised, but I was hoping to curcumvent that if at all possible.

rotund pasture
#

to clarify, the flow isn't really direct bank-to-bank. What happens in the situation of a Separate Charge and Transfer (SCT) flow is that the customer funds go into the platform's Stripe balance, and then the platform transfers funds to the connected account(s). Subsequently, those funds are paid out to the connected account's bank account on file for payouts.

wary jewel
#

Ok, that's more or less the documentation I was looking for.

rotund pasture
#

you can't circumvent that limit so you would need to reach out to Stripe Support to request for the limit to be raised