I remember the first time I evaluated a payments platform for a startup: the promise of seamless payouts, embedded finance and a clean API felt like magic. Stripe Treasury is one of those platform-level offerings that can accelerate product development and unlock new revenue streams. But the convenience comes with responsibilities—especially around liquidity and compliance. Over the years I’ve seen founders rush into integrations without asking the right questions, and pay for it later with frozen funds, unexpected holdbacks, or regulatory headaches. Here are the practical, targeted questions I now always ask (and recommend you ask) before integrating Stripe Treasury—or any custodial banking/embedded finance product—into your business.

Who technically holds the funds and where are they custodied?

This is the foundational question. On paper, Stripe Treasury partners with banks (like Evolve Bank & Trust in the U.S. historically) to custody funds. But you need to know:

  • Is Stripe acting as a service provider while a bank holds customer deposits, or is Stripe the direct custodian for my end-users’ balances?
  • Which bank(s) are used and in what jurisdictions are those banks chartered?

    • Why it matters: Custody determines the applicable deposit protections (e.g., FDIC insurance in the U.S.), insolvency exposure, and the legal process if a bank or service provider gets into trouble. If funds are pooled, you should know the pooling structure and the priority of claims.

    What are the custody and liquidity mechanics during normal operations and stress events?

    Ask for a clear description of the lifecycle of funds: how deposits are received, where they sit overnight, how quickly you can move money between ledgers, and what happens during bank settlement windows. Also drill into stress scenarios:

  • What are the withdrawal timelines for customers and for my business?
  • Are there daily or monthly limits? Are there treasury-level controls that can freeze payouts?
  • What happens to pending transactions if the partner bank faces a payment network issue or insolvency?

    • I always request flow diagrams and SLAs in writing. It’s not enough to be told “it’s fast”—get the exact expected timeframes.

    Who bears the compliance burden—me, Stripe, the bank, or all of us?

    Compliance can be split across multiple parties. You need to map responsibilities across KYC/AML, sanctions screening, suspicious activity reporting (SAR), and tax reporting. Questions to ask:

  • Which party conducts customer due diligence (CDD)?
  • Who files CTRs/SARs or equivalent reports in the relevant jurisdictions?
  • What level of KYC will be required for end-users vs. business accounts?

    • In practice, you often share responsibilities. If your product gives users the ability to hold balances, regulators will expect your company to have AML/KYC processes even if Stripe or the bank performs the checks. That means budget for compliance tooling and possibly a compliance officer.

    What triggers holds or freezes on funds, and what is the escalation process?

    Hidden liquidity risk often comes from unexpected holds. Ask for clear examples of triggers and what the remediation process looks like:

  • Automated risk flags (volume spikes, high chargebacks, suspicious flow patterns)
  • Regulatory holds (sanctions, law enforcement requests)
  • Bank-internal risk controls (atypical routing, mismatch of account details)

    • Then ask:

  • How will I be notified?
  • How fast can holds be resolved or lifted?
  • Is there a dedicated support tier for enterprise issues?

    • I insist on written policies and a named escalation contact when possible. Vague “we’ll review and get back to you” is not sufficient when customer funds are involved.

    What are the fees, and are there embedded or pass-through charges that can reduce apparent liquidity?

    Fees can be more complex than they seem. Beyond per-transaction fees, ask about:

  • Monthly custody or ledger fees
  • Network settlement fees
  • Returned item/chargeback fees
  • Interest treatment—who gets the float interest?

    • Make sure you understand net settlement versus gross settlement. In some setups, fees are deducted before settlement so your available balance may be smaller than expected. Build conservative cash forecasts that assume worst-case fee scenarios while you’re still early.

    How is user data shared and what are the privacy implications?

    Compliance and privacy overlap. Clarify what data Stripe and the partner bank will collect, how long it’s retained, and who can access it:

  • Are PCI, GDPR, or other local data requirements met?
  • How is sensitive financial data stored and transmitted?

    • If you operate across borders, be explicit about cross-border data transfer mechanisms and lawful bases for processing. Missteps here can trigger fines and operational restrictions.

    What reporting and reconciliation capabilities will I have?

    Liquidity surprises are often reconciliation surprises. Ask for the exact reporting primitives:

  • Is there an API to pull real-time ledger balances and transaction-level detail?
  • Are there daily settlement reports, statements, and timezone specifics?
  • Can I export data in formats compatible with my accounting system?

    • I insist on programmatic access to ledger balances and a sandbox that includes realistic settlement delays so my finance team can build resilient processes from day one.

    Who owns the customer relationship and who is responsible for customer support?

    If Stripe or the bank will interact directly with your users, clarify the boundary of customer support. Misaligned expectations can create reputational risk and escalate into compliance events. Ask:

  • Will KYC/verification requests come from Stripe/the bank or from you?
  • Who handles disputes, queries about balances, and fraud investigations?

    • Define SLAs and the handoff process. Often you’ll need to be the first line of support, but the bank may need to be looped in for account-level actions.

    What are the regulatory and licensing constraints in each jurisdiction I operate in?

    Embedded finance is jurisdictionally complex. For each market you target, verify:

  • Do I require a local license to offer stored value or e-money?
  • Are there foreign-exchange restrictions or reserve requirements?
  • How do consumer protection laws affect wallet features (interest-bearing accounts, overdrafts)?

    • I build a jurisdiction matrix early in the planning phase. It helps prioritize markets and determines whether the product needs to be geofenced or modified per region.

    Can I migrate away later, and what is the exit strategy for retrieving customer funds?

    Finally, always plan for the endgame. Ask about data portability, account closures, and bulk fund migrations:

  • What is the process and timing to migrate customer balances to another provider or bank?
  • Are there penalties for terminating the contract?
  • What data will be available for customers to take to another provider?

    • Contracts should include clear exit provisions that protect your users’ access to funds and avoid a scenario where money is trapped because of technical or contractual friction.

    Risk Area Key Questions to Ask Practical Mitigation
    Custody Who holds funds? Which bank? Is there deposit insurance? Verify bank charters; require documentation of custodian arrangements.
    Liquidity How fast can funds move? What holds exist? Test in sandbox; set conservative cash buffers; negotiate SLAs.
    Compliance Who handles AML/KYC? Reporting responsibilities? Map responsibilities; budget for compliance tooling and staff.
    Operational What reporting and support are available? Require robust APIs, daily statements, and named escalation contacts.

    Integrating Stripe Treasury can be transformative, but it’s not just a technical decision—it’s a strategic and regulatory one. I always advise founders to approach these integrations like partnerships, not plug-and-play services. Insist on documentation, test in environments that reflect production realities, and make sure your legal and finance teams review contract terms with these specific questions in mind. If you want, I can share a checklist or a sample contract clause template that I use when evaluating treasury integrations—just tell me which jurisdiction your startup operates in and I’ll tailor it.