mattcomroe_api | Stripe Developers | Page 1

crystal crowBOT Jun 17, 2025, 9:26 PM

#

👋 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/1384645510622613504

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

astral badge Jun 17, 2025, 9:28 PM

#

Hi there

#

Unfortunately there is no good way to do this other than waiting the necessary time period. The best thing to do for testing payouts is to actually mock the API response for your tests.

sonic moon Jun 17, 2025, 9:30 PM

#

well that's a bummer but i understand

#

and what about the grouping of transactions and what determines that? CC in one bucket and everything bank related in another?

astral badge Jun 17, 2025, 9:31 PM

#

I think the other option is that you can ask our Support team to speed up an automatic payout in test mode. I think (though not 100% certain) that they have the tooling to do this. You would contact them through https://support.stripe.com/contact/login -- but my opinion is still that mocking is the best way to go.

#

Oh sorry, missed that second part of the question.

sonic moon Jun 17, 2025, 9:31 PM

#

no problem! i usually try and ask only one thing at a time anyway. :D.

astral badge Jun 17, 2025, 9:32 PM

#

Are you using our legacy Charges flow for ACH?

#

Or do you use PaymentMethods + PaymentIntents?

sonic moon Jun 17, 2025, 9:32 PM

#

i'd have to double check but i'm pretty sure we're fully on PaymentMethods/PaymentIntents

#

(looking now.. will take me a minute to see if we have those calls in our codebase or not)

#

so the "new" thing that somehow is causing problems for us is we've started onboarding more payment methods of "us_bank_account" type.

astral badge Jun 17, 2025, 9:33 PM

#

Gotcha, in this case the available_on of the Balance Transaction (https://docs.stripe.com/api/balance_transactions/object#balance_transaction_object-available_on) dictates when funds would be included in a Payout

#

Also of note you will only be able to have Balance Transactions linked to a Payout if you use Automatic payouts

#

(As the error that you encountered noted)

#

With Manual Payouts it breaks that "linking"

sonic moon Jun 17, 2025, 9:35 PM

#

yes that's what got me here. figured i'd ask about the other stuff while i was at it.

#

our /Charges/ POST call seems to be dead; nothing references it anymore so i think i was right that we're fully off of using that API.

astral badge Jun 17, 2025, 9:36 PM

#

Gotcha, then yeah all funds are paid out together in source_type: "card"

#

Regardless of being ACH or Card

#

So really just the available_on would dictate when those funds are paid and what Payout they are in.

sonic moon Jun 17, 2025, 9:38 PM

#

oh interesting. i think we're doing some grouping on our end that we don't need to anymore then...

#

because what's happening in our reconciliation process is that only transactions that are from a "us_bank_account" source are somehow getting missed.

#

this is pretty exciting. i might be able to cut out a whole bunch of useless logic.

astral badge Jun 17, 2025, 9:40 PM

#

Yeah with the legacy ACH flow we had to isolate the balance into a separate source_type. But with our new ACH v2 (PaymentIntents + PaymentMethods) flow that limitation was removed and the funds are just grouped into the card balance with everything else.

sonic moon Jun 17, 2025, 9:41 PM

#

so just to re-state to make sure i've got what you're saying.. because we only use PaymentIntents API, transactions will get linked to payouts as the funds are available (if that's the right way to put it).. regardless of the funding source; credit card, debit card, etc. Everything comes through from you as source_type = "card" so that's all I'll need to expect on my end and don't need to check for "ach_debit" or whatever any other value of that would have been.

astral badge Jun 17, 2025, 9:42 PM

#

Yep (the value would be bank_account: https://docs.stripe.com/api/balance/balance_object#balance_object-available-source_types-bank_account but yes that's now irrelevant since you don't use legacy ACH)

sonic moon Jun 17, 2025, 9:46 PM

#

oh, but maybe we do? we have long-standing customers that created "old" ACH Source objects.. i know we had migrations of certain types of those (SEPA Debit), but the issue I'm having is with US-based customers... so could there still be a mix of new and old ACH accounts being used that would still be generating payouts with the bank_account source_type?

#

i'm sure i can figure this out on my dashboard...

#

either way the issue i'm having totally fits this pattern.. means that i need to group the "us_bank_account" type PMs into the "cards" bucket because i think right now it's expecting bank_account which is why they're getting orphaned in the reconciliation.

astral badge Jun 17, 2025, 9:47 PM

#

Only if you use /v1/charges -- if you only use PaymentIntents then it should all reconcile to card still regardless of using Bank Accounts or PaymentMethods.

astral badge Jun 17, 2025, 9:48 PM

#

sonic moon either way the issue i'm having totally fits this pattern.. means that i need to...

Yep

#

It sounds likely that is the culprit here

sonic moon Jun 17, 2025, 9:49 PM

#

i can't thank you enough. our reconciliation code pre-dates me and as you can imagine is quite a pile of edge cases. I think you just helped me crack this nut and I'm so grateful!

astral badge Jun 17, 2025, 9:50 PM

#

Happy to help!

sonic moon Jun 17, 2025, 9:54 PM

#

i've got nothing else; thanks so much for your time and help! i appreciate you! enjoy the rest of your day.

#mattcomroe_api