#taiki_api

1 messages · Page 1 of 1 (latest)

tiny relicBOT
#

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

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

#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.

fickle echo
#

(Continuation of my question above — it got cut off)

My two questions are:

  1. Does settlement_timing.delay_days_override apply to funds received via Destination Charges (transfer_data.destination)? My understanding is it only applies to on_behalf_of or direct charges — is that correct?
  2. If Destination Charges don't respect delay_days_override, what is the recommended approach to enforce a 30-day hold? Should I switch to on_behalf_of, or use Separate Charges & Transfers with a scheduled 30-day delayed transfer?

Note: Despite confirmed Balance Settings (delay_days_override: 30, interval: manual), payments via Destination Charges appear available in the Express Dashboard within ~10 days, not 30.

tiny relicBOT
radiant elm
#

hello!

Does settlement_timing.delay_days_override apply to funds received via Destination Charges (transfer_data.destination)? My understanding is it only applies to on_behalf_of or direct charges — is that correct?

Yes, delay days only apply to destination charges with on_behalf_of and direct charges : https://docs.stripe.com/connect/manage-payout-schedule#delay_days

If Destination Charges don't respect delay_days_override, what is the recommended approach to enforce a 30-day hold? Should I switch to on_behalf_of, or use Separate Charges & Transfers with a scheduled 30-day delayed transfer?

It really depends on your use case - using on_behalf_of has certain implications : https://docs.stripe.com/connect/destination-charges?platform=web&ui=elements#settlement-merchant

fickle echo
#

Thanks for clarifying!

To hold funds on the platform for 30 days (for chargeback mitigation) before allowing the connected account to manually withdraw:

  1. Is "Separate Charges and Transfers" considered the best practice for this specific use case?
  2. If I use "Separate Charges and Transfers", do I have to build my own scheduled worker (e.g., cron job) to trigger the stripe.transfers.create() API exactly 30 days later? Or is there any built-in Stripe feature that can automatically delay this transfer for me?