#jmontydesign - Transfer
split hemlock
Do you mean a Transfer ($ moves from your Stripe Account to the Connected Stripe Account) or a Payout (from Connected Stripe Account to External Bank Account)?
tight kestrel
My understanding is that stripe.transfers.create transfers the funds immediately from our platform to the connected customer's custom account. Our custom connected account (invisible to our customer) now holds the transfer funds and is set to automatic payouts daily. Is there any way for our app to know the status of the payment after the initial transfer to the custom connected account so that we can let the customer know in our app.?
split hemlock
You mean of the transfer to their account or of the daily payout?
If you just want to let them know about the transfer to their Stripe account you can review the associated balance_transaction that is in the returned object in the API when you create the transfer.
tight kestrel
After our platform transfers the money to the custom connect account? Can our platform know anything more about the status of when the money is transfered to the connected account's bank account?
split hemlock
You can even request that this record be included in the returned object from the API by specifying expand: [balance_transaction] as one of the parameters.
Ok, the Payout then.
It really helps to use specific language here. There are a lot of ways to move money with our APIs and they behave differently for each one. 🙂
You can list the payouts of your connected account using our Payouts API, using the Stripe Account header: https://stripe.com/docs/api/payouts/list
Alternatively you could set up Connect webhook endpoints to listen for the payout.paid event and use that to trigger notifications to your connected account.
https://stripe.com/docs/api/events/types#event_types-payout.paid
tight kestrel
Thanks! Separate question: The transfer object returned includes: "source_transaction: null,
source_type: 'card'," . My intention is that the trnasfer be made from the platform's balance that has been "topped up", where is the "card" source_type coming from?
split hemlock
Is that the question or a preface?
tight kestrel
I'm testing "topping up" up our platform account balance from the test bank account (done) and making a transfer to a test Connect account without specifying a source, since I expected it to come from the platform balance. When I make the transfer I get a return object that has these two properties:
"source_transaction: null,
source_type: 'card',"
I'm confused by the source_type saying "card". 1)Is that the default? 2)When I looked into the possibilities for adding a source_type parameter in the transfer call, I see "card", "bank_account" and "npx". Since I am expecting to use the platform's balance, I'm not sure what the source_type should be?
split hemlock
Just curious, do you have any request IDs for these tests?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
tight kestrel
{
id: 'tr_1KRMQiIlkDnuVFxuz3pC0cVw',
object: 'transfer',
amount: 40000,
amount_reversed: 0,
balance_transaction: 'txn_1KRMQiIlkDnuVFxucSwWYQR3',
created: 1644437180,
currency: 'usd',
description: 'Roo shift 9433',
destination: 'acct_1KPcf1RAXsTbhQ4A',
destination_payment: 'py_1KRMQiRAXsTbhQ4A9rjUEfoT',
livemode: false,
metadata: { shiftGroupId: '9433', businessName: 'my vet business_2' },
reversals: {
object: 'list',
data: [],
has_more: false,
total_count: 0,
url: '/v1/transfers/tr_1KRMQiIlkDnuVFxuz3pC0cVw/reversals'
},
reversed: false,
source_transaction: null,
source_type: 'card',
transfer_group: '9433'
}
polar vortex
yeah card is the default!
source_type can be card or bank_account and the latter is only used for funds collected via ACH Debit for compliance reasons, otherwise everything goes in source_type: 'card'
tight kestrel
I'm currently creating custom connect test accounts with only the "transfer" capability. In order for the auto payment to occur to the customer's bank account, do I need to add an additional capability. We are only using thes custom connect accounts to pay our customers with the goal of getting the money into their bank account as quickly as possible.
polar vortex
no you don't need to do anything else
tight kestrel
Thanks!
Re: "Alternatively you could set up Connect webhook endpoints to listen for the payout.paid event and use that to trigger notifications to your connected account."
I understand the process of setting up webhooks for our platform ... providing our webhook handling endpoint in the dashboard, will the connected account's payout.paid event be triggered in our platform's webhook events? Or are you saying I have to set up webhooks in all of our thousands of customers' connected accounts? If so can that be done in the custom Connect account creation process, by sending our webhook handling endpoint?
polar vortex
You create one webhook endpoint in your account of type Connect and you automatically get events for all connected accounts on that endpoint
tight kestrel
fantastic! If the webhook is listening for the payout.paid event, how can I link it to the transferId returned when I make the initial transfer ...if mulptile transfers have been made, is there a way from the webhook to know if the payout includes funds from what transfers?