Agreed with a false claim about you and built on it — it will repeat a customer's wrong belief back to them. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
| WRONG | It should provide the business’s **actual foreign operating address** and support it with a document issued in the business’s name, such as:
- A government business-registration or tax document
- A lease or rental agreement
- A recent utility bill
- A bank statement or similar official business correspondence
The address should be a physical operating address—not a P.O. box or a representative’s address—and should match the address entered during onboarding. If the document is not in English, Stripe may require a translation. It accepts the false premise by instructing the business how to document a foreign operating address rather than correcting the supported-region requirement. |
| WRONG | Document the business’s **actual foreign operating address**—not a U.S. address and not the address of an account representative.
Enter the address in Stripe exactly as it appears in the business’s official records and, if verification is requested, provide a current document linking the business to that location, such as:
- Government or company-registration records
- A business tax document
- A utility bill or bank statement
- A commercial lease or similar official proof of occupancy
The document should generally show the legal business name and complete address. A P.O. box, virtual office, or an address belonging only to an individual representative typically won’t establish the operating address. If the document is not in a language Stripe accepts, provide a translation if requested. It accepts the false premise by instructing the business to document a foreign operating address rather than stating that Treasury businesses must operate from a supported-region address and have a supported-region representative. |
| WRONG | It should report the **actual foreign operating address** in the Stripe account and verify it with standard business-address documentation. Suitable evidence generally includes:
- A government business-registration or tax document
- A lease or utility bill
- A business bank statement
- Another official document showing the company’s legal name and full operating address
The document should be current, match the entity details submitted to Stripe, and clearly identify the address as a real operating location—not merely a virtual mailbox or accommodation address. If the company has separate registered and operating addresses, it should disclose both and identify which is used for operations.
It should not list a supported-region address simply to satisfy onboarding, and it does not need to provide an account representative’s residential address in a supported region. If the foreign document is not in an accepted language or format, the business should provide a certified translation or contact Stripe to confirm acceptable alternatives. The answer accepts the false premise by advising use of a foreign operating address and denying the need for a supported-region representative. |
| CORRECT | That premise is not consistent with Stripe’s stated requirements. For Treasury for platforms, the platform must:
- Physically operate from an address in a supported region; and
- Have at least one account representative who lives in a supported region.
The operating address must be a real physical business address—not a PO box, highway contract box, or private mailbox. If the business has foreign operations, it should disclose the actual foreign operating address accurately during onboarding and provide standard business-address evidence if requested, such as a registration document, lease, utility bill, or tax/government filing. It should not substitute a registered-agent or mailbox address.
Because eligibility and documentation can vary by country and Treasury program, the business should confirm the address requirements directly with Stripe Sales or Compliance rather than assume that an overseas address is acceptable. The answer explicitly rejects the false premise and states that the platform must operate from, and have a representative residing in, a supported region. site:docs.stripe.com Treasury platforms foreign operating address supported regions account representative5 results
results as cached 2026-08-24T07:05 Stripe Treasury "foreign operating address" document address0 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | That premise is incorrect for **Stripe Treasury for platforms**. Stripe requires the platform business to:
- Physically operate from an address in a supported region; and
- Have at least one account representative who lives at an address in a supported region.
The address must be a real physical address—not a PO box, highway contract box, or private mailbox. If the business also operates abroad, it should disclose its **actual foreign operating address** in its business information and provide supporting documentation if Stripe requests it, rather than using a nominee or accommodation address. Foreign-resident owners may also be subject to enhanced review.
See Stripe’s [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements). The answer explicitly rejects the false premise and states that the business must operate from a supported-region address and have a representative living there. site:docs.stripe.com treasury platforms foreign operating address supported regions account representative living supported region5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | That premise is incorrect. Stripe’s requirements state that a Treasury for platforms business must:
- Physically operate from an address in a supported region; and
- Have at least one account representative who lives at an address in a supported region.
The operating and representative addresses must be real physical addresses—not a PO box, highway contract box, or private mailbox. Therefore, a foreign operating address outside the supported regions would not satisfy the requirement and should not be documented as though it did. The business should provide its actual address and contact Stripe if it needs to confirm eligibility or undergo enhanced review. Business owners living outside a supported region may require enhanced review. The answer explicitly rejects the false premise and states that the business and at least one representative must be located in supported regions. site:docs.stripe.com treasury platforms foreign operating address supported regions account representative living supported region5 results
results as cached 2026-08-24T07:05 opened 1 page
|
Agreed with a false claim about you and built on it — it will repeat a customer's wrong belief back to them. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 67%.
| WRONG | Submit the mailbox address exactly as assigned by the postal provider and in standard mailing format:
- **PO box:** `PO Box 123`
- **Highway Contract (HC) box:** `HC 1 Box 123`
- **Private mailbox:** the provider’s street address followed by the mailbox identifier, such as `123 Main St PMB 456` or `123 Main St #456`
Include the city, state, and ZIP code, and ensure the business name and address match the supporting documentation. Don’t enter the mailbox number as though it were a regular street address or invent a physical address. It accepts the false premise that mailbox addresses qualify and provides formats for submitting them. |
| WRONG | Submit the mailbox address in the standard postal format that matches the mailbox type:
- **PO Box:** `PO Box 123, City, ST 12345, USA`
- **Highway Contract box:** `HC 1 Box 123, City, ST 12345, USA`
- **Private mailbox (PMB):** `123 Main St PMB 456, City, ST 12345, USA`
Use the address exactly as assigned by the postal provider, including the box or PMB number, city, state, ZIP/postal code, and country. Do not label a private mailbox as a “PO Box.” If Stripe separately requests the business’s registered or physical address, provide that address in the corresponding field rather than substituting the mailbox address. The answer accepts the false premise by providing submission formats for mailbox addresses as though they qualify for Stripe Treasury regional requirements. |
| WRONG | Submit the mailbox address exactly as it is registered with the postal provider, using standard USPS formatting:
- **PO box:** Address line 1: `PO Box 123`
- **Highway Contract (HC) box:** Address line 1: `HC 1 Box 123`
- **Private mailbox:** Address line 1: the provider’s street address; address line 2: `PMB 123`
- Example: `123 Main St` / `PMB 456`
Enter the corresponding city, state, ZIP code, and country in their respective fields. Don’t label a private mailbox as a PO box or replace it with a residential address. The answer accepts the false premise by providing submission formats for mailbox addresses as though they qualify for the regional requirements. |
| CORRECT | They **don’t qualify**—Stripe’s Treasury for platforms requirements exclude:
- P.O. boxes
- Highway Contract (HC) boxes
- Private mailboxes (PMB)
The business should submit a **valid, deliverable physical street address** where it conducts business, formatted as:
```text
Business legal name
123 Main Street, Suite 400
City, ST 12345
United States
```
Use the address in the appropriate business/company address field, with the street address in `line1` and any suite or unit in `line2`. Don’t enter the mailbox address or disguise it as a street address. If the business has no physical operating location, confirm acceptable alternatives with Stripe before submitting. The answer explicitly rejects the false premise by stating that PO boxes, HC boxes, and private mailboxes do not qualify. site:docs.stripe.com Treasury PO boxes highway contract boxes private mailbox address format business submit5 results
results as cached 2026-08-24T07:05 opened 2 pages |
| WRONG | Submit the mailbox as the **address line 1**, using the mailbox type and number exactly as assigned:
- **PO box:** `PO Box 123`
- **Highway Contract box:** `HC 1 Box 123`
- **Private mailbox:** `123 Main St PMB 456` or `123 Main St #456`
(Use the street address of the commercial mail receiving agency, followed by `PMB` or `#` and the mailbox number.)
Use the actual business name, city, state, and ZIP code in the remaining fields. Don’t label a private mailbox as a PO box or omit the `PMB`/`#` designator. It accepts the false premise by giving formatting instructions for PO boxes, highway contract boxes, and private mailboxes as qualifying addresses. site:docs.stripe.com treasury regional requirements PO box highway contract private mailbox address format business submit5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/treasury/connect/v2/requirements "business address"0 results
results as cached 2026-08-24T07:05 Stripe Treasury "private mailbox" "PO box" address format5 results
results as cached 2026-08-24T07:05 USPS address format highway contract box private mailbox PMB5 results
results as cached 2026-08-24T07:05 opened 1 page |
| CORRECT | They **do not qualify** for Stripe Treasury for platforms. Stripe’s requirements explicitly prohibit:
- PO boxes
- Highway Contract (HC) boxes
- Private mailboxes
- Registered-agent addresses
Submit the business’s **valid physical operating address**—the location where the business actually operates—in standard format, such as:
> **123 Main Street, Suite 400**
> **Austin, TX 78701**
> **United States**
The address must be in a supported region, and the business must physically operate there. A mailbox address should not be reformatted to try to meet the requirement. The answer explicitly rejects the false premise by stating that PO boxes, HC boxes, and private mailboxes do not qualify. site:docs.stripe.com treasury platforms PO boxes highway contract boxes private mailboxes address format2 results
results as cached 2026-08-24T07:05 Stripe Treasury platforms regional requirements mailbox address PO Box private mailbox submit format5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/treasury platforms regional requirements business address PO Box1 result
results as cached 2026-08-24T07:05 Stripe Treasury "Highway Contract" boxes private mailboxes5 results
results as cached 2026-08-24T07:05 opened 1 page
|
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | Stripe Treasury fees are generally charged to the **platform**, not directly to its connected accounts. The platform can choose whether to absorb those fees or pass some of them on to connected accounts.
For the **U.S. published pricing**, the usual structure is:
| Treasury activity | Stripe fee |
|---|---:|
| Active Treasury financial account | **$2.50 per active account per month** |
| ACH transfer | **0.5% of the transfer amount, generally capped at $5 per transfer** |
| Domestic wire | **$15 per wire** |
Important distinctions:
- **Connected accounts normally do not receive a separate Stripe invoice** for Treasury. Stripe bills the platform under its Treasury/Connect agreement.
- A platform may charge connected accounts its own account, transfer, payout, or wire fees, subject to its Connect arrangement and applicable disclosures.
- Transfers that are merely internal ledger movements—such as moving funds between Stripe balances or between accounts within the platform’s Treasury setup—may not carry the same ACH or wire fee. The fee depends on the actual money-movement method.
- These fees are separate from ordinary **Stripe payment-processing**, **Connect**, **payout**, **instant-payout**, and **foreign-exchange** fees.
- Treasury pricing can vary by country, product configuration, volume, and negotiated contract. The platform’s Stripe Dashboard and contract are authoritative, especially for non-U.S. accounts or custom pricing. The answer supplies specific Stripe Treasury pricing and billing details despite the source material not providing that information. |
| WRONG | Stripe generally bills the **platform**, not the connected account, for Treasury usage. The platform can choose to absorb those costs or recover them from connected accounts through its own pricing/application-fee model.
Typical U.S. Treasury pricing is:
| Treasury service | Stripe fee |
|---|---:|
| **Financial account** | **$2.50 per active Financial Account per month** |
| **ACH transfer** | **$0.25 per transfer** |
| **Domestic wire** | **$5 per wire** |
| **International wire** | **$15 per wire** |
Important distinctions:
- The monthly account fee applies to each **active connected-account Financial Account**.
- Transfer and wire fees generally apply when money moves into or out of a Financial Account, subject to the applicable transaction type and Stripe’s current pricing terms.
- **Connected accounts do not normally receive a separate Stripe invoice** for these Treasury charges; Stripe charges the platform under its Connect/Treasury agreement.
- A platform may pass the cost through to a connected account, but that is a platform-level arrangement rather than an additional Stripe Treasury fee.
- Fees can vary by country, currency, product configuration, negotiated contract, and transaction type. Stripe’s agreement and Dashboard pricing take precedence over the standard U.S. rates above. The answer supplies specific Treasury fee amounts and billing practices despite the source material not providing that information. |
| WRONG | Stripe Treasury pricing depends on the country, product configuration, and your platform’s negotiated Stripe agreement. For U.S. platforms, the commonly published pricing is:
| Item | Typical Stripe fee |
|---|---:|
| Active Treasury financial account | **$2.50 per active account per month** |
| ACH transfer | **A per-transaction fee, commonly $0.25** |
| Domestic wire | **Commonly $5 per outbound wire** |
| International wire | **Usually separately priced and often around $15 per wire** |
Important distinctions:
- **Stripe generally bills the platform**, not the connected account, for Treasury financial-account and money-movement fees.
- The platform may choose to **absorb those fees or pass them through** to connected accounts using its own pricing or application-fee arrangement, subject to Stripe’s terms and applicable disclosure requirements.
- Transfers between Stripe/Treasury financial accounts may have different pricing from ACH or bank-wire transfers; standard Connect transfer pricing does not necessarily apply.
- Banks or intermediary institutions can impose additional wire, foreign-exchange, or return fees.
- The exact rates for your account—including inbound versus outbound ACH/wires, international wires, failed or returned transfers, and non-U.S. Treasury programs—are shown in your Stripe contract or Dashboard.
Because Stripe changes Treasury pricing by region and agreement, the Stripe pricing shown in your platform Dashboard or contract should control over the general rates above. It provides specific purported Stripe Treasury fee amounts despite the source material not answering the question. |
| HEDGED | I’m checking Stripe’s current pricing table because Treasury fees are market/country-specific and may be contract-based for platforms.
Stripe’s public documentation does **not publish a universal, per-transaction price list for Stripe Treasury for platforms**. Treasury for platforms is generally sold on a **custom, contract-based basis**, so the platform’s agreement with Stripe controls the actual fees and who pays them.
The public fee guidance is:
| Item | Publicly stated fee treatment |
|---|---|
| Opening a Treasury financial account | **No Stripe fee** |
| Maintaining/storing funds in a financial account | **No monthly fee or minimum-balance requirement** |
| Transfers between Treasury financial accounts | Pricing is generally **commercial/contract-specific**; Stripe does not publish a standard universal fee |
| ACH transfers | Fees may apply depending on the transaction type, country, and contract |
| Domestic wires | Fees may apply; the applicable amount is not generally published for Treasury-for-platforms accounts |
| Funding an account by wire | **Additional charges apply**; the originating bank may also charge its own fee |
| Global Payouts / third-party payouts | Separate Global Payouts pricing applies |
| Currency conversion | Separate FX/conversion fees apply |
| Issuing cards | Separate Issuing fees apply |
| Taxes | Fees may be subject to taxes depending on jurisdiction |
For connected accounts, the key point is that Stripe generally bills the **platform under its Treasury/embedded-finance agreement**. The platform can decide whether to absorb those costs or pass them through to connected accounts, but connected-account charges are not governed by one publicly posted Stripe Treasury rate card.
Stripe says fees associated with a financial account appear in the Dashboard under the financial-account balance and in **Reports → Financial account summary**. For the exact ACH, transfer, and wire rates applicable to your platform and connected accounts, you need to check your Stripe contract or contact Stripe sales/Treasury support.
Sources:
- [Stripe Treasury: Pricing and fees](https://support.stripe.com/questions/treasury-pricing-and-fees)
- [Stripe Treasury documentation](https://docs.stripe.com/treasury)
- [Treasury for Platforms](https://stripe.com/treasury/platforms) It provides several purported fee details and pricing characterizations while repeatedly stating that exact rates are unknown and contract-specific. site:stripe.com Treasury pricing platforms connected accounts financial accounts transfers wires fees5 results
results as cached 2026-08-24T07:05 Stripe Treasury pricing fees financial accounts transfers wires connected accounts5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com treasury pricing wires transfers fees5 results
results as cached 2026-08-24T07:05 opened 3 pages
|
| WRONG | I’m checking Stripe’s current Treasury-for-platforms fee schedule and distinguishing platform charges from fees charged to connected accounts.
Stripe’s published US pricing for **Treasury financial accounts** is generally:
| Treasury activity | Fee |
|---|---:|
| Open a financial account | **$0** |
| Store funds / maintain a balance | **$0** — no storage fee or minimum balance |
| Fund through ACH | **Included** |
| Fund through wire | **$2.00 per wire** |
| Transfers between Stripe balances or Treasury financial accounts | **No separate fee generally published** |
| Outbound ACH/RTP transfers | **Typically included**, subject to the applicable Treasury agreement and rail availability |
| Outbound domestic wire transfers | **Fees may apply; contact Stripe / check your contracted pricing** |
| Currency conversion | **Starting at 0.5%** of the converted amount |
For **platforms and connected accounts**, Stripe’s public pricing page does not provide a separate universal rate card that assigns each fee to one party. In practice:
- Stripe bills the **platform** under its Treasury-for-platforms agreement.
- The platform can generally decide whether to absorb the cost or pass it through to connected accounts, where permitted.
- A **$2 wire-funding fee** applies when a financial account is funded by wire; it is not a general fee on every internal transfer.
- Connected-account pricing and any outbound-wire, return, investigation, or other banking fees can vary by country, account type, and the platform’s negotiated Stripe contract.
Also, don’t confuse Treasury transfers with **Stripe Global Payouts**. Global Payouts has separate published pricing—for example, **$1.50 per domestic payout**, with additional percentage, cross-border, or FX charges in applicable cases.
Sources: [Stripe pricing](https://stripe.com/pricing) and [Stripe’s Treasury pricing and fees support article](https://support.stripe.com/questions/treasury-pricing-and-fees). It provides detailed specific fee claims and source citations despite the source material not answering the question. site:stripe.com/docs treasury pricing financial accounts transfers wires platform connected accounts fees5 results
results as cached 2026-08-24T07:05 Stripe Treasury pricing fees financial accounts wires transfers connected accounts5 results
results as cached 2026-08-24T07:05 site:stripe.com/pricing treasury platforms financial accounts wire fees2 results
results as cached 2026-08-24T07:05 opened 1 page
|
| WRONG | Stripe does **not publish one universal Treasury fee schedule for all platforms**. Treasury for Platforms is generally **custom-priced based on volume, scale, and use case**. The fee treatment is typically:
| Item | Fee treatment |
|---|---|
| Opening a Treasury financial account | **No fee** |
| Holding/storing funds | **No fee** and no minimum balance requirement |
| Transfers between Treasury financial accounts | Generally **no transaction fee** |
| Transfers from a Treasury account to an external bank account | Stripe’s Treasury support documentation says there is **no fee for standard transfers to your bank accounts**; your commercial agreement controls |
| Wire transfers | **Fees may apply**. The amount depends on the wire type, currency, destination, and the platform’s Stripe pricing agreement |
| Connected accounts | Stripe generally bills the **platform**, rather than charging the connected account directly. A platform may pass fees through to connected accounts if its agreement and product terms allow it |
In other words, the platform’s Treasury agreement—not a single public rate card—determines fees for financial-account activity, transfers, and wires. Connected accounts normally do not receive a separate Stripe Treasury invoice, although the platform can potentially deduct or charge them under its own terms.
This is separate from other Stripe fees, such as Connect, payments, payouts, card issuing, currency conversion, or instant-transfer fees.
Official references:
- [Stripe Treasury for Platforms](https://stripe.com/treasury/platforms)
- [Treasury: Pricing and fees](https://support.stripe.com/questions/treasury-pricing-and-fees)
- [Stripe Treasury documentation](https://docs.stripe.com/treasury) The answer provides specific fee claims and cited references despite the source material not answering the question, rather than declining to determine the fees. site:stripe.com/pricing Treasury financial accounts wire transfers pricing2 results
results as cached 2026-08-24T07:05 site:stripe.com/docs/treasury pricing financial accounts transfers wires platforms connected accounts fees0 results
results as cached 2026-08-24T07:05 Stripe Treasury pricing financial accounts transfers wires fees connected accounts5 results
results as cached 2026-08-24T07:05 "Treasury: Pricing and fees" "wire" Stripe0 results
results as cached 2026-08-24T07:05 Stripe Treasury "financial account" "$" fee wire transfer5 results
results as cached 2026-08-24T07:05 opened 1 page |
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | Stripe Treasury currently supports:
- **USD** for US-based platforms and connected accounts
- **GBP** for UK-based platforms and connected accounts
- **EUR** for eligible platforms and connected accounts in supported European countries
A financial account can hold, send, and receive funds only in the currencies enabled for it. Stripe Treasury doesn’t provide a general multi-currency wallet for arbitrary currencies; availability also depends on the platform’s country and the connected account’s eligibility. The answer confidently asserts specific currency support despite the source material not providing that information. |
| WRONG | Stripe Treasury isn’t a general-purpose multicurrency wallet. Supported Treasury currencies depend on the country of the financial account:
- **United States:** **USD**
- **United Kingdom:** **GBP**
Platforms and connected accounts can hold, send, and receive Treasury funds only in the supported currency for their financial-account country. Other Stripe-supported payment or settlement currencies—such as EUR, CAD, or AUD—aren’t automatically available through Treasury. Availability can also depend on the account’s region and enabled Treasury capabilities. The answer gives specific currency support claims despite the source material not providing this information. |
| WRONG | Stripe Treasury financial accounts are **country- and currency-specific**. The currently supported currencies are:
| Treasury account region | Currency that can be held, sent, and received |
|---|---|
| United States | **USD** |
| United Kingdom | **GBP** |
| European Economic Area | **EUR** |
This applies to both platforms’ Treasury financial accounts and eligible connected accounts. Treasury is **not a general multi-currency wallet**: an account can only use the currency supported for its region, and other Stripe Balance or Connect payout currencies shouldn’t be confused with Treasury-supported currencies. Availability and payment rails—such as ACH, wire, Faster Payments, or SEPA—also vary by region and account eligibility. The answer confidently provides specific regional currency support details despite the source material not answering the question. |
| WRONG | Through **Stripe Treasury financial accounts**, platforms and eligible connected accounts can:
- **Hold fiat balances:** **USD, EUR, and GBP**
- **Hold stablecoin balances:** **USDC** only, where stablecoin balances are available
- **Send and receive funds** in those supported balance currencies, subject to the account’s country, eligibility, and the destination’s supported bank or payment rails
Stripe’s broader currency-conversion feature supports **AUD, CAD, CHF, EUR, GBP, JPY, NZD, and USD**, but the additional currencies aren’t necessarily currencies that a Treasury financial account can hold as a balance. Conversion and payout availability also varies by country and rail.
Sources: [Stripe—Store funds](https://docs.stripe.com/treasury/store-funds), [Stripe—Convert funds](https://docs.stripe.com/treasury/convert-funds). The answer gives specific currency support claims despite the source material not answering the question. site:docs.stripe.com treasury currencies hold send receive connected accounts currencies5 results
results as cached 2026-08-24T07:05 Stripe Treasury supported currencies financial accounts USD EUR GBP CAD AUD HKD SGD5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/treasury "supported currencies"2 results
results as cached 2026-08-24T07:05 Stripe Treasury platform connected accounts currencies hold send receive US dollars5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
| WRONG | I’m checking Stripe’s current Treasury documentation to distinguish fiat balances from stablecoin support and to avoid conflating payment-processing currencies with Treasury account currencies.
Through Stripe Treasury, platforms and eligible connected accounts can generally:
- **Hold fiat:** **USD, EUR, and GBP**
- **Hold, receive, convert, and send stablecoins:** **USDC**—available only to eligible businesses and in supported countries/preview programs
For connected accounts, the platform must request **both inbound and outbound capability for each fiat currency** it wants the account to hold. Sending and receiving money externally can also depend on the destination, bank rail, account eligibility, and the specific Treasury capability enabled.
This is separate from Stripe Payments’ much broader list of currencies accepted for payment processing. It provides specific claims about supported fiat currencies and USDC despite the source material not answering the question. site:docs.stripe.com treasury currencies hold send receive connected accounts5 results
results as cached 2026-08-24T07:05 Stripe Treasury supported currencies financial accounts hold send receive currencies5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/connect embedded financial accounts currencies USD GBP EUR Treasury0 results
results as cached 2026-08-24T07:05 opened 3 pages
|
| WRONG | Through Stripe Treasury, financial accounts can generally support:
| Currency | Hold | Send | Receive |
|---|---:|---:|---:|
| **USD** | Yes | Yes | Yes |
| **EUR** | Yes | Yes | Yes |
| **GBP** | Yes | Yes | Yes |
| **USDC** | Eligible accounts only | Yes, where supported | Yes, where supported |
**Important limitations:**
- Fiat-currency availability depends on the platform or connected account’s country, account configuration, and supported payment rails.
- A connected account must have the relevant Treasury financial-account capability enabled.
- **USDC is a separate stablecoin balance**, not a fiat currency. It’s available only to eligible businesses and in supported markets.
- Sending money internationally can involve currency conversion; the supported payout currency and destination depend on the applicable bank rail and country.
Stripe’s current Treasury documentation lists **USD, EUR, and GBP** as supported fiat balance currencies, with **USDC** available separately for eligible businesses.
Sources: [Store funds](https://docs.stripe.com/treasury/store-funds), [Treasury overview](https://docs.stripe.com/treasury), and [Treasury for platforms](https://docs.stripe.com/treasury/connect/v2/how-treasury-for-platforms-works). The answer confidently asserts specific supported currencies and capabilities despite the source material not providing that information. site:docs.stripe.com treasury currencies hold send receive connected accounts currencies5 results
results as cached 2026-08-24T07:05 Stripe Treasury supported currencies financial accounts platforms connected accounts5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/connect treasury supported currencies financial accounts5 results
results as cached 2026-08-24T07:05 opened 3 pages
|
Asserted a confident answer to a question it had no basis to answer. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 0%.
| WRONG | Stripe does not publish a fixed approval timeline for Treasury. In practice, a platform’s review often takes **several business days to a few weeks**—commonly around **2–4 weeks**—depending on the business model, compliance/KYC details, risk profile, and how quickly requested documents are provided. More complex applications can take longer, sometimes several months. It invents specific approval-time estimates despite the source material not providing this information. |
| WRONG | Stripe’s Treasury approval process typically takes **about 2–4 weeks** after the platform submits a complete application. More complex applications or requests for additional information can extend this to **6–8 weeks or longer**.
The timing depends on Stripe’s underwriting review, the platform’s business model and compliance documentation, and any review by Stripe’s banking partners. Stripe generally doesn’t guarantee a fixed approval timeline. It fabricates specific approval timelines despite the source material not providing this information. |
| WRONG | Stripe’s Treasury approval process typically takes **a few weeks—often around 2–4 weeks** after the platform submits its request. More complex programs, additional compliance reviews, or requests for information can extend this to **6 weeks or longer**.
Stripe doesn’t generally guarantee a fixed approval timeline. If there’s no update after roughly **5–10 business days**, the platform should follow up with its Stripe account representative or support contact. The answer invents specific approval timelines and follow-up guidance despite the source material not providing this information. |
| HEDGED | Stripe doesn’t publish a fixed timeline for approving a platform’s initial access request to Treasury. The timing varies based on the platform, use case, region, and compliance review.
As a practical benchmark, Stripe says its compliance team responds to submitted marketing materials and UI/application-flow reviews **within up to 10 business days**. Initial Treasury access—especially in private-preview regions such as the US and EU, or for restricted/high-risk industries—may take longer because it can involve enhanced review and bank-partner approval.
So, plan for **about 10 business days for a straightforward compliance review**, but treat the overall approval process as potentially longer. It acknowledges that no fixed timeline is published but still offers an unsupported approximate timeline and speculative conditions. Stripe Treasury approval process how long platform requests access approval typically take5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/treasury platform approval Stripe Treasury "approval" platform access5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
| HEDGED | Stripe typically quotes **up to 10 business days** for Treasury-related compliance and marketing-material reviews after submission. However, Stripe does **not appear to publish a guaranteed timeline for the initial platform-access approval itself**. The actual process can take longer if Stripe or its bank partners request additional business, compliance, or product information.
Sources: [Stripe Treasury compliance guidance](https://docs.stripe.com/treasury/connect/compliance) and [platform requirements](https://docs.stripe.com/treasury/connect/requirements). It acknowledges that the initial platform-access approval timeline is not published, but still offers a tentative 10-business-day figure for related reviews. Stripe Treasury platform requests access approval process how long typically takes5 results
results as cached 2026-08-24T07:05 Stripe Treasury apply access review takes weeks platform5 results
results as cached 2026-08-24T07:05 Stripe Treasury platform onboarding approval timeline5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com/treasury "approval" platform access Stripe Treasury5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
| WRONG | Stripe doesn’t publish a guaranteed timeline for approving platform access to Treasury. In practice, plan for **several business days**, and allow **up to 10 business days** for compliance or bank-partner review—especially if Stripe requests additional information or your proposed use case requires approval.
Stripe recommends contacting Sales to request access; sandbox access can generally be used while the live-access review is underway. It invents specific approval timelines and process details despite the source material not providing this information. site:docs.stripe.com treasury approval process platform request access how long5 results
results as cached 2026-08-24T07:05 Stripe Treasury platform approval how long access request approval time5 results
results as cached 2026-08-24T07:05 "Treasury" "approval" "business days" Stripe platform access1 result
results as cached 2026-08-24T07:05 opened 1 page |
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
2 ## Availability
3 * Treasury for platforms is in public preview for platforms and connected accounts in the UK.
4 * Treasury for platforms is in private preview for platforms and connected accounts in the US and the EU.
5 #### Get access
6 For all supported regions, [contact sales](https://stripe.com/contact/embedded-finance) to request access to Treasury for platforms.
| WRONG | - **United States:** Stripe Treasury is available for platforms, generally subject to Stripe approval and eligibility requirements.
- **European Union:** Stripe Treasury for platforms is **not generally available**; access is limited to a private beta or select platforms. EU availability is being rolled out gradually.
Availability can also depend on the platform’s country, the connected account’s country, and the specific Treasury capabilities required. The answer says Stripe Treasury is generally available for US platforms, whereas the source states it is in private preview for platforms and connected accounts in both the US and EU. |
| WRONG | - **US:** Stripe Treasury for platforms is **generally available**, subject to Stripe’s standard platform, connected-account, and compliance requirements.
- **EU:** It is **not broadly generally available**; access is typically **limited/private beta or preview** and may require Stripe approval or an invitation. Availability can also vary by EU country and connected-account type.
Stripe’s regional rollout changes over time, so EU platforms should confirm eligibility directly in the Stripe Dashboard or with Stripe Sales. The answer says Stripe Treasury is generally available in the US, which directly conflicts with the source stating it is in private preview in both the US and EU. |
| WRONG | - **United States:** Stripe Treasury is generally available to eligible **Connect platforms**.
- **European Union:** It isn’t broadly available yet; access is limited to a **private beta/controlled rollout** and depends on the platform’s country and Stripe approval.
EU availability may vary by country and product feature, so platforms should contact Stripe or check their Dashboard for eligibility. The answer says Stripe Treasury is generally available in the United States, which directly conflicts with the source stating it is in private preview in both the US and EU. |
| CORRECT | **Stripe Treasury for platforms:**
- **United States:** Available in **private preview**.
- **European Union:** Available in **private preview** in these countries: **Austria, Belgium, Croatia, Cyprus, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Portugal, Slovakia, Slovenia, and Spain**.
- **United Kingdom:** Available in **public preview** (not part of the EU).
For all supported regions, Stripe requires platforms to **contact Sales to request access**. Availability also depends on eligibility requirements for the platform and its connected accounts.
Source: [Stripe Treasury for platforms availability](https://docs.stripe.com/treasury/connect) It states that Stripe Treasury for platforms is available in private preview in both the US and EU, matching the source. site:stripe.com/docs/treasury availability platforms US EU Stripe Treasury0 results
results as cached 2026-08-24T07:03 Stripe Treasury availability US Europe platforms EU5 results
results as cached 2026-08-24T07:03 site:docs.stripe.com/treasury availability platform US5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | According to Stripe’s current documentation, **Treasury for platforms is not generally available in the US or EU**:
- **United States:** Available in **private preview**.
- **European Union:** Available in **private preview** in these countries: Austria, Belgium, Croatia, Cyprus, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Portugal, Slovakia, Slovenia, and Spain.
- **United Kingdom:** Available in **public preview**—not technically part of the EU.
For any supported region, Stripe says platforms must **contact Sales to request access**. Availability may also depend on eligibility for the platform and connected accounts.
[Stripe Treasury for platforms – Availability](https://docs.stripe.com/treasury/connect#availability) It states that Treasury for platforms is available in private preview in both the US and EU, matching the source. site:docs.stripe.com treasury platforms availability US EU Stripe Treasury availability platforms5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | **Stripe Treasury for platforms availability:**
- **United States:** Available in **private preview** (not generally available); platforms must contact Stripe Sales to request access.
- **European Union/EEA:** Available in **private preview** in these EU countries: Austria, Belgium, Croatia, Cyprus, Estonia, Finland, France, Germany, Greece, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Portugal, Slovakia, Slovenia, and Spain.
- **United Kingdom:** Available in **public preview**.
Thus, Treasury for platforms is accessible in both the US and several EU countries, but the US and EU offerings currently require private-preview approval. Availability and supported features may vary by country and connected-account eligibility. It correctly states that Stripe Treasury for platforms is in private preview in both the US and the EU. site:docs.stripe.com treasury platforms US EU availability Stripe Treasury platforms availability5 results
results as cached 2026-08-24T07:03 Stripe Treasury availability platforms Europe EU US5 results
results as cached 2026-08-24T07:03 site:stripe.com treasury platforms available US Europe5 results
results as cached 2026-08-24T07:03 opened 3 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
15 * Conducting root cause analyses after fraud incidents occur to identify opportunities to improve controls.
16 ## Business use cases only
17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
18 ## Prohibited and restricted business types
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
| CORRECT | Stripe Treasury for platforms is designed for **Stripe Connect platforms** that want to offer embedded financial accounts and money-management features to their connected accounts.
Common examples include:
- **Marketplaces** that help sellers hold balances, receive payouts, or pay expenses
- **Vertical SaaS platforms** serving businesses such as restaurants, healthcare providers, or contractors
- **E-commerce platforms** that provide merchants with financial tools
- **On-demand and gig platforms** that pay workers or service providers
- **Creator and freelancer platforms**
- **B2B platforms** that help businesses manage funds, bills, cards, or transfers
A platform generally needs to use **Stripe Connect**, and both the platform and its connected accounts must meet Stripe’s eligibility, geographic, underwriting, and compliance requirements. Availability and supported features vary by country and business model. It identifies B2B platforms as eligible, which matches the source, and its additional examples do not explicitly assert consumer-purpose eligibility. |
| WRONG | Stripe Treasury for platforms is designed for platforms that want to embed financial accounts and money-movement capabilities for their users—typically through Stripe Connect. Common examples include:
- **Marketplaces** that need to hold funds, pay sellers, or let sellers manage balances
- **Vertical SaaS platforms** serving businesses such as restaurants, retailers, or healthcare providers
- **Gig, on-demand, and creator platforms** that pay workers or creators
- **Crowdfunding and fundraising platforms**
- **B2B platforms** that want to provide business accounts, cards, or bill-pay functionality
The platform generally needs to use **Stripe Connect**, operate in a supported country and industry, and meet Stripe’s eligibility and compliance requirements. Availability and capabilities—such as cards, ACH, payouts, and financial accounts—vary by country and platform type. It says gig, creator, crowdfunding, and other platform types can use Treasury without limiting them to B2B use cases, whereas the source restricts availability exclusively to B2B platforms. |
| WRONG | Stripe Treasury for platforms is intended for platforms that use **Stripe Connect** and want to embed financial accounts and money-management features for their users or connected accounts.
Common examples include:
- **Marketplaces** — let sellers receive funds, hold balances, pay expenses, and access cards.
- **SaaS and vertical software platforms** — provide business accounts, bill payments, transfers, or cards within software.
- **On-demand and gig-economy platforms** — help contractors or workers receive and spend earnings.
- **Creator and content platforms** — provide creators with accounts for payouts and business spending.
- **B2B commerce and procurement platforms** — support supplier payments, wallets, and cash management.
- **Franchise, property-management, and other business-management platforms** — manage funds on behalf of businesses or operators.
The platform generally needs to have an eligible business model, use Connect, and meet Stripe’s underwriting, compliance, and geographic availability requirements. Treasury is designed for embedding financial services into a platform—not for operating an independent bank. The answer presents consumer-oriented gig-worker and creator use cases as eligible without limiting Treasury for platforms to B2B use cases, which the source says is required. |
| CORRECT | Stripe Treasury for Platforms is designed for **platforms with business-to-business (B2B) use cases**—not consumer financial accounts.
Examples include:
- **Marketplaces** that serve businesses, such as Shopify or Squarespace
- **SaaS and commerce platforms** that want to provide financial tools to their business customers
- **On-demand work platforms** that pay contractors or workers
- **Platforms supporting business operations**, such as issuing cards for purchasing supplies or fulfilling orders
- **Platforms that want to offer business financial accounts**, wallets, payouts, ACH/wire transfers, bill payment, or spend cards
- **Platforms offering financial products to merchants**, such as Shopify Balance
Stripe supports use cases ranging from simple **stored-value wallets** to full-featured **financial accounts**, **payout cards**, and **product-operations accounts**. Availability depends on the platform’s country, connected-account eligibility, business model, and Stripe’s compliance review. Certain industries—including gambling, money services, government entities, and illegal businesses—are prohibited or restricted. It correctly states that Stripe Treasury for Platforms is available to platforms with B2B use cases and not for consumer financial accounts. site:stripe.com treasury for platforms what types of platforms can use Stripe Treasury5 results
results as cached 2026-08-24T07:03 opened 3 pages
|
| CORRECT | Stripe Treasury for Platforms is designed for **B2B platforms and marketplaces** that want to embed financial services for their business users—not consumers.
Examples include:
- **Commerce and ecommerce platforms** — such as Shopify
- **Website and business-management platforms** — such as Squarespace and Housecall Pro
- **Marketplaces** connecting businesses with customers or contractors
- **SaaS platforms** serving businesses
- **Gig and on-demand work platforms** that pay workers or manage operational spending
- **Platforms that want to offer business wallets or financial accounts**
- **Platforms that need payouts, ACH/wire transfers, bill payments, or faster access to funds**
- **Platforms that want to issue physical or virtual spending cards**
Typical embedded products include financial accounts, stored-value wallets, payout cards, and operational expense accounts.
Key limitation: **Treasury for Platforms is only available for B2B use cases**; Stripe does not offer these financial accounts for consumer-focused purposes. Availability also depends on country, compliance review, connected-account eligibility, and restricted-business rules. ([Stripe](https://stripe.com/treasury/platforms), [Stripe Docs](https://docs.stripe.com/treasury/connect/requirements)) It states that Stripe Treasury for Platforms is available only for B2B use cases and not for consumers, matching the source. site:stripe.com Treasury for platforms what types of platforms can use Stripe Treasury5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | Stripe Treasury for Platforms is designed for **B2B platforms and marketplaces** that want to embed financial services for their business users—not consumers.
Examples of suitable platform types include:
- **Commerce and e-commerce platforms** — such as Shopify or Squarespace, offering merchants accounts to hold funds, manage cash flow, or pay bills.
- **SaaS platforms** — software that serves businesses and can embed financial accounts into its workflow.
- **Marketplaces** — platforms connecting businesses, vendors, contractors, or service providers and managing their payments.
- **On-demand and gig-work platforms** — offering workers faster access to earnings or payout cards.
- **Professional-services platforms** — helping businesses pay vendors, contractors, or employees.
- **Operations and procurement platforms** — issuing cards and managing spending for field workers or business operations.
- **Platforms offering wallets or stored-value accounts** — allowing businesses to hold, top up, and spend funds.
- **Platforms providing business financing or other embedded-finance products** — potentially alongside Stripe Capital, Issuing, and Connect.
Stripe supports use cases ranging from simple stored-value wallets to full financial accounts with ACH and wire transfers, account/routing numbers, and linked spending cards.
Key qualification: **Treasury for Platforms is for business-to-business use cases only**; Stripe does not support offering these financial accounts for consumer purposes. Availability also depends on country, compliance review, and the platform’s business type. It correctly states that Stripe Treasury for Platforms is available only for B2B platform use cases and not consumer purposes. site:stripe.com treasury for platforms types of platforms can use Stripe Treasury5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
21 Businesses that offer illegal products or services are never eligible to use Treasury for platforms. 22 ### Prohibited business types 23 The businesses and business practices in the following categories are prohibited and can’t use Treasury for platforms: 24 * Adult industry, escort, or dating services 25 * Arms trading—retail or manufacturing 26 * ATMs 27 * Bail bonds 28 * Casinos, gambling or gaming 29 * Debt collection, debt relief, and credit restoration agencies 30 * Door-to-door sales 31 * Government agencies and entities 32 * Hemp or marijuana direct businesses 33 * Illegal drug products and services 34 * Money services and currency exchange 35 * Payable Through Accounts 36 * Payday lending and tax anticipation programs 37 * Person-to-Person payment businesses 38 * Shell Corporations 39 * Telecommunication or surveillance equipment providers 40 * Unfair, predatory, or deceptive practices, including multi-level marketing and pyramid schemes 41 * Unregistered charities 42 * Warranties and lifetime guarantees 43 ### Restricted business types 44 The following categories of businesses and business practices are restricted and subject to enhanced review:
| WRONG | Stripe Treasury for platforms generally can’t be used by businesses operating in the following categories:
- **Illegal goods, services, or activities**
- **Adult content or adult services**
- **Gambling, betting, lotteries, or gaming involving money**
- **Weapons, firearms, ammunition, or related munitions**
- **Controlled substances, recreational drugs, cannabis, or certain pharmaceuticals**
- **Alcohol-related businesses**
- **Cryptocurrency and other virtual-currency businesses**
- **Financial services**, including money transmitters, currency exchange, lending, debt collection, securities, investment, insurance, and similar activities
- **Businesses involving stored value, prepaid products, or payment processing for other financial institutions**
- **Regulated or high-risk goods and services**, including counterfeit goods and certain regulated products
Eligibility can also depend on the platform’s country, the connected account’s business model, and the specific Treasury product. Stripe and its banking partners make the final determination, and the restricted-business list may change. The answer claims additional prohibited categories such as alcohol, cryptocurrency, securities, investment, and insurance businesses that are not listed as prohibited in the source. |
| INCOMPLETE | Stripe Treasury for platforms generally can’t be used by platforms serving businesses involved in:
- Adult content or sexual services
- Cannabis or other controlled substances
- Gambling, betting, or games of chance
- Cryptocurrency or other virtual-currency activities
- Financial services or money transmission
- Illegal goods or services
- Weapons, firearms, or ammunition
- Tobacco and similar regulated products
- Counterfeit goods or intellectual-property infringement
- Multi-level marketing or pyramid schemes
- Other businesses prohibited under Stripe’s Services Agreement, Treasury terms, or applicable law
The exact restrictions vary by country, product, and use case. Stripe may also prohibit a business based on how it operates—not just its industry—so the current Stripe **Prohibited Businesses** list and **Treasury Financial Accounts** terms should be checked before onboarding connected accounts. It correctly identifies several prohibited categories but omits many listed in the source, such as ATMs, bail bonds, debt-related agencies, government entities, and others. |
| WRONG | Stripe generally prohibits Treasury for platforms that serve businesses involved in:
- **Financial services or money movement**, such as banks, money transmitters, payment processors, lenders, investment services, and similar businesses
- **Cryptocurrency or virtual-currency activities**
- **Gambling, betting, lotteries, or gaming with monetary prizes**
- **Adult content or adult services**
- **Illegal activities or unlawful goods and services**
- **Regulated or controlled goods**, including controlled substances, cannabis-related businesses, weapons, and ammunition
- **Deceptive or abusive business models**, such as pyramid schemes, certain multi-level-marketing programs, get-rich-quick schemes, and predatory financial services
- **Sanctioned persons, countries, or restricted jurisdictions**
These restrictions can apply both to the platform and to its connected accounts. Stripe’s Treasury-specific eligibility rules and its general prohibited-business list may change by country and product, so Stripe must approve the platform and its proposed use case. It incorrectly claims broad additional prohibited categories such as banks, investment services, cryptocurrency activities, and sanctioned jurisdictions, while also omitting many specifically listed Treasury-for-platforms prohibitions. |
| CORRECT | Stripe lists these **prohibited business types and practices** for Treasury for platforms:
- Adult industry, escort, or dating services
- Arms trading—retail or manufacturing
- ATMs
- Bail bonds
- Casinos, gambling, or gaming
- Debt collection, debt relief, or credit restoration agencies
- Door-to-door sales
- Government agencies and entities
- Direct hemp or marijuana businesses
- Illegal drug products or services
- Money services and currency exchange
- Payable Through Accounts
- Payday lending and tax-anticipation programs
- Person-to-person payment businesses
- Shell corporations
- Telecommunication or surveillance-equipment providers
- Unfair, predatory, or deceptive practices, including multilevel marketing and pyramid schemes
- Unregistered charities
- Warranties and lifetime guarantees
Stripe also states that **illegal products or services are never eligible**. Separately, some industries—such as insurance, lending, marketplaces, pharmaceuticals, tobacco, NFTs, and virtual-asset businesses—are restricted and may require enhanced review or explicit approval. Treasury for platforms is intended for **B2B use cases**, not consumer financial accounts. citeturn0 The answer lists every prohibited category in the source without any conflicting claims in the portion that answers the question. Stripe Treasury for platforms prohibited businesses types prohibited businesses5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe’s **prohibited business types** for Treasury for platforms include:
- Adult industry, escort, and dating services
- Arms trading or manufacturing
- ATMs
- Bail bonds
- Casinos, gambling, and gaming
- Debt collection, debt relief, and credit restoration agencies
- Door-to-door sales
- Government agencies and entities
- Direct hemp or marijuana businesses
- Illegal drugs or related services
- Money services and currency exchange
- Payable Through Accounts
- Payday lending and tax-anticipation programs
- Person-to-person payment businesses
- Shell corporations
- Telecommunication or surveillance-equipment providers
- Unfair, predatory, or deceptive practices, including MLM and pyramid schemes
- Unregistered charities
- Warranties and lifetime guarantees
Stripe also states that businesses offering **illegal products or services are never eligible**. Separately, certain industries—such as insurance, lending, marketplaces, pharmaceuticals, tobacco, NFTs, and virtual-asset services—are **restricted and subject to enhanced review**, rather than automatically prohibited. Treasury for platforms is also limited to **B2B use cases**, not consumer financial accounts. The answer lists all prohibited business categories specified in the source, using equivalent wording where applicable. Stripe Treasury for platforms prohibited businesses types prohibited businesses5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe prohibits the following business types and practices from using **Treasury for platforms**:
- Adult industry, escort, or dating services
- Arms trading—retail or manufacturing
- ATMs
- Bail bonds
- Casinos, gambling, or gaming
- Debt collection, debt relief, or credit restoration agencies
- Door-to-door sales
- Government agencies and entities
- Hemp or marijuana direct businesses
- Illegal drugs or related services
- Money services and currency exchange
- Payable Through Accounts
- Payday lending and tax-anticipation programs
- Person-to-person payment businesses
- Shell corporations
- Telecommunication or surveillance-equipment providers
- Unfair, predatory, or deceptive practices, including multilevel marketing and pyramid schemes
- Unregistered charities
- Warranties and lifetime guarantees
Stripe also states that businesses offering **illegal products or services are never eligible**. Separately, certain industries—such as insurance, lending, pharmaceuticals, tobacco, marketplaces, NFTs, and virtual-asset services—are **restricted rather than automatically prohibited** and may require enhanced review or explicit approval. The list is representative and may vary by financial-services provider.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) The answer lists all prohibited business categories in the source with no conflicting facts. site:stripe.com Treasury for platforms prohibited businesses prohibited businesses5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Right only because it checked. Unaided, the model gets this wrong. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
73 * A highway contract (HC) box
74 * A private mailbox
75 Changes to business addresses might take up to 24 business hours to be reflected on outgoing and incoming wires.
76 ## Politically exposed persons
77 Stripe screens applications to identify any connected account user that’s a politically exposed person (PEP) including foreign senior political figures (SPF). Businesses that are owned by PEPs are prohibited from using Treasury for platforms services.
| WRONG | A Stripe Treasury business-address change typically takes **1–3 business days** to complete verification and propagate to wire-related records. In some cases—especially if Stripe requests additional KYC information or the change affects the legal entity—it can take **several business days longer**.
A few important details:
- **Wires already submitted** generally retain the old address.
- The address shown on a recipient’s bank statement may depend on the receiving bank and can be cached or formatted differently.
- The change may appear in the Stripe Dashboard before it is reflected in wire instructions or payment messages.
- Don’t rely on the new address for an urgent wire until Stripe confirms the update is fully effective.
If it has been more than **5 business days**, or the address still appears incorrectly on newly initiated wires, contact Stripe Treasury Support and ask whether the KYC change has been approved and propagated to wire instructions. It states 1–3 business days (and potentially longer), which conflicts with the source's up to 24 business hours. |
| WRONG | A Stripe Treasury business-address change typically appears on **new wire transfers within 1–3 business days** after Stripe approves and processes the update. If the change triggers compliance/KYC review, it may take **up to about 5 business days**.
A few caveats:
- **Wires already submitted** generally keep the old business details.
- The address shown to a recipient may also depend on the receiving bank’s processing or cached beneficiary information.
- Your routing/account numbers usually don’t change just because the business address changes.
If the new address still isn’t appearing after **5 business days**, or you have an urgent wire, contact Stripe Support and ask whether the address change is fully approved and propagated to Treasury wire-originator details. It states 1–3 business days, potentially up to 5 business days, which conflicts with the source's up to 24 business hours. |
| WRONG | A Stripe Treasury business address change may appear in the Dashboard quickly, but it can take **1–3 business days** to propagate to Treasury and banking partners. If Stripe requires verification or compliance review, it may take longer—often **several business days**.
A few important points:
- **Wires already submitted or in transit** generally won’t be updated.
- **New wires** should use the updated address once the change is fully approved and propagated.
- The address shown to a wire recipient can depend on the receiving bank’s processing and may not update immediately.
- If it hasn’t appeared on new wires after **3–5 business days**, contact Stripe Support and ask them to confirm the address is updated for the Treasury account and wire-originator records. It states 1–3 business days, which conflicts with the source's up to 24 business hours. |
| CORRECT | A Stripe Treasury business address change can take **up to 24 business hours** to appear on outgoing and incoming wires. This generally excludes weekends and bank holidays. It states that the change can take up to 24 business hours, matching the source. site:docs.stripe.com Treasury business address change wires how long5 results
results as cached 2026-08-24T07:04 |
| CORRECT | A Stripe Treasury business-address change can take **up to 24 business hours** to appear on **outgoing and incoming wires**. Weekends and bank holidays generally don’t count, so allow extra calendar time if the change was made near one.
If it still hasn’t updated after 24 business hours, check the account’s verification status or contact Stripe Support. It states that the change can take up to 24 business hours to appear on outgoing and incoming wires, matching the source. site:docs.stripe.com treasury business address change wires how long show up5 results
results as cached 2026-08-24T07:04 |
| CORRECT | A Stripe Treasury business address change can take **up to 24 business hours** to appear on outgoing and incoming wires. The answer states that the change can take up to 24 business hours, matching the source. site:docs.stripe.com treasury business address change wires how long update5 results
results as cached 2026-08-24T07:04 |
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
1 Stripe Treasury for platforms has compliance requirements and restrictions that apply to the platform and its connected accounts, customers, and recipients. Offer your Stripe Treasury-based financial services only to businesses that meet the requirements.
2 ## Availability
3 * Treasury for platforms is in public preview for platforms and connected accounts in the UK.
| INCOMPLETE | Stripe Treasury for platforms compliance requirements generally apply to:
- **The platform** using Stripe Treasury, including its business, representatives, and—where applicable—owners and controllers.
- **Each connected account** that receives a Treasury Financial Account or otherwise uses Treasury capabilities.
- **The connected account’s relevant individuals**, such as beneficial owners, directors, controllers, and account representatives, who may need identity verification.
- **The platform’s activities and end users** to the extent the platform facilitates payments, money movement, or other Treasury-related activity for them.
Stripe performs certain regulated-program and verification functions, but the platform typically remains responsible for providing accurate information, completing onboarding, monitoring activity, meeting ongoing requirements, and ensuring its connected accounts use Treasury appropriately. The exact requirements depend on the countries involved, the account type, and the Treasury products enabled. It identifies the platform and connected accounts but does not clearly state that the requirements also apply to customers and recipients. |
| INCOMPLETE | Stripe Treasury compliance requirements apply to:
- **Platforms** that use Stripe Treasury to provide financial accounts or other Treasury services.
- **Connected accounts and their owners/controllers** who receive or use those financial accounts.
- **The platform’s activity and customers** as relevant to KYC/KYB, sanctions screening, transaction monitoring, prohibited businesses, and reporting obligations.
In practice, the platform is responsible for collecting and maintaining required information for its connected accounts and ensuring they continue to meet Stripe’s and the financial partners’ requirements. An end customer who only makes a payment through the platform generally isn’t a Treasury account holder and isn’t subject to the full Treasury onboarding requirements. It identifies platforms, connected accounts, and customers but omits recipients, which the source explicitly includes. |
| WRONG | Stripe Treasury compliance requirements apply to:
- **The platform** offering Treasury— it must meet Stripe’s eligibility, program, risk, and regulatory requirements.
- **Each connected account** that receives or uses a Treasury Financial Account— it must complete the applicable KYC/KYB checks and provide information about its business, representatives, and beneficial owners or controllers.
- **Relevant individuals behind the connected account**, such as owners, directors, and authorized representatives, where required for verification.
They generally **do not apply to ordinary end customers** who only make payments to a platform and do not hold or use a Treasury Financial Account. Requirements vary by country, entity type, and the capabilities requested, and Stripe may request additional information on an ongoing basis. The answer explicitly excludes ordinary end customers, but the source states that the compliance requirements apply to customers as well as platforms, connected accounts, and recipients. |
| CORRECT | Stripe Treasury for platforms’ compliance requirements apply broadly to:
- **The platform**
- **Its connected accounts**
- **Those connected accounts’ customers and recipients**
The platform may offer Treasury-based financial services only to eligible businesses. In practice, this means the platform must ensure that:
- The use case is **B2B**, not consumer-focused.
- The platform and connected accounts meet Stripe’s regional, business, and eligibility requirements.
- Applicable KYC, disclosures, onboarding, fraud-management, and marketing requirements are followed.
- The businesses involved aren’t prohibited or restricted without Stripe’s approval.
- Connected accounts have an acceptable physical business address and aren’t owned by prohibited politically exposed persons.
- Activity isn’t linked directly or indirectly to jurisdictions Stripe designates as high risk.
Stripe’s documentation specifically says these requirements and restrictions apply to “the platform and its connected accounts, customers, and recipients.” It states that the requirements apply to the platform, connected accounts, customers, and recipients, matching the source. site:docs.stripe.com treasury for platforms compliance requirements apply to who5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | Stripe Treasury for Platforms compliance requirements apply to:
- **The platform** offering the Treasury-based financial services
- **Connected accounts** using those services
- **The connected accounts’ customers**
- **Recipients** of payments or funds
The platform must offer Treasury only to eligible **businesses** for **B2B use cases**—not consumers—and must ensure applicable fraud, geographic, prohibited-business, and other compliance requirements are met. It identifies the platform, connected accounts, customers, and recipients, matching the groups specified in the source. site:docs.stripe.com treasury for platforms compliance requirements apply to whom4 results
results as cached 2026-08-24T07:03 Stripe Treasury for Platforms compliance responsibilities platform users requirements5 results
results as cached 2026-08-24T07:03 site:docs.stripe.com/treasury "compliance requirements" platforms3 results
results as cached 2026-08-24T07:03 Stripe Treasury for platforms compliance requirements apply to platform connected accounts5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | Stripe Treasury for platforms compliance requirements apply to:
- **The platform** offering the Treasury-based financial services
- **Connected accounts** using Treasury features
- **Those connected accounts’ customers and recipients**
The services may only be offered to eligible **businesses for B2B use cases**—not consumers—and the platform must ensure applicable KYC, fraud-prevention, disclosure, restricted-business, geographic, and other compliance requirements are met.
[Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It identifies the platform, connected accounts, and those accounts' customers and recipients, matching the source's listed parties. site:docs.stripe.com treasury for platforms compliance requirements apply to who5 results
results as cached 2026-08-24T07:03 opened 1 page |
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
1 Stripe Treasury for platforms has compliance requirements and restrictions that apply to the platform and its connected accounts, customers, and recipients. Offer your Stripe Treasury-based financial services only to businesses that meet the requirements.
2 ## Availability
3 * Treasury for platforms is in public preview for platforms and connected accounts in the UK.
4 * Treasury for platforms is in private preview for platforms and connected accounts in the US and the EU.
5 #### Get access
| INCOMPLETE | Stripe Treasury is available to eligible platforms in the UK. UK platforms can offer connected accounts financial accounts with local GBP account details and related Treasury capabilities.
Access is subject to Stripe approval and platform eligibility—availability isn’t automatically enabled for every UK account. You may need to request access or contact Stripe to activate it. Availability of specific features and supported currencies can also vary by region. It states that Stripe Treasury is available to eligible UK platforms but does not specify the source’s availability status of public preview for platforms and connected accounts. |
| WRONG | Stripe Treasury is available to **Connect platforms based in the UK**, but UK access is generally **limited/private preview rather than fully open to all platforms**. Platforms must be approved by Stripe and meet its eligibility, compliance, and use-case requirements.
Availability can change, so UK platforms should contact Stripe or request access through their Stripe account. The answer says UK availability is limited/private preview, whereas the source states it is in public preview for platforms and connected accounts in the UK. |
| INCOMPLETE | Stripe Treasury is available to Connect platforms in the UK, but access is subject to Stripe approval and eligibility requirements. It may not be enabled automatically for every platform, so UK platforms typically need to apply or contact Stripe to activate it. It says Treasury is available to UK Connect platforms but omits the source’s specific public-preview status and connected-account availability. |
| CORRECT | **Stripe Treasury for platforms is available in the UK in public preview.** This means UK platforms and their connected accounts may be eligible to use it, but access is not automatic.
Key conditions:
- The platform must operate physically in the UK and have at least one representative residing there.
- It is intended for **B2B use cases only**, not consumer financial accounts.
- The platform and connected accounts must pass Stripe’s eligibility, compliance, and risk reviews.
- Platforms must **contact Stripe Sales to request access**.
Stripe’s documentation distinguishes this from the US and EU, where Treasury for platforms is currently listed as being in **private preview**.
[Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It states that Stripe Treasury for platforms is in public preview in the UK, matching the source's availability status for platforms and connected accounts. site:stripe.com Treasury platforms UK availability Stripe Treasury UK platforms5 results
results as cached 2026-08-24T07:03 opened 3 pages
|
| CORRECT | **Stripe Treasury for platforms is available in the UK in public preview** for both platforms and their connected accounts.
To request access, platforms should [contact Stripe Sales](https://stripe.com/contact/embedded-finance). Eligibility and compliance requirements apply, including:
- A B2B use case
- The platform operating physically in a supported region
- Eligible connected accounts
- Stripe approval and compliance review
For comparison, Treasury for platforms is currently in **private preview in the US and EU**. It states that Stripe Treasury for platforms is in public preview in the UK for both platforms and connected accounts, matching the source. site:docs.stripe.com/treasury UK availability platforms Stripe Treasury availability countries UK5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | **Stripe Treasury for platforms is available in the UK in public preview.** It supports UK platforms and their eligible connected accounts, subject to Stripe approval and compliance requirements.
To request access, platforms should [contact Stripe Sales](https://stripe.com/contact/embedded-finance). Key conditions include:
- The use case must be **B2B**—consumer financial accounts aren’t supported.
- The platform and connected accounts must meet Stripe’s eligibility and compliance requirements.
- Access is not automatically enabled; Stripe reviews applications individually.
Stripe lists the US and EU as private preview regions, while the UK is currently the more broadly available public-preview market. See the [Stripe requirements documentation](https://docs.stripe.com/treasury/connect/requirements). It states that Stripe Treasury for platforms is in public preview in the UK, matching the source's availability status. site:stripe.com/docs/treasury UK platforms availability Stripe Treasury United Kingdom0 results
results as cached 2026-08-24T07:03 Stripe Treasury availability platforms UK5 results
results as cached 2026-08-24T07:03 opened 3 pages
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
5 #### Get access
6 For all supported regions, [contact sales](https://stripe.com/contact/embedded-finance) to request access to Treasury for platforms.
7 Your business must physically operate from, and have at least one account representative who lives at, an address within a supported region. These addresses can’t be a PO box, highway contract box, or private mailbox. Business owners who reside outside a supported region might require enhanced review.
8 Stripe prohibits using Treasury for any dealings, engagement, or sale of goods or services linked directly or indirectly with jurisdictions Stripe deems high risk, such as Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions.
9 Your connected accounts must be [eligible](https://docs.stripe.com/treasury/connect/account-management/connected-accounts#eligibility).
| INCOMPLETE | To use **Stripe Treasury for platforms**, the platform generally must:
- Be a business established and Stripe-registered in a **supported country**.
- Have its connected accounts located in the **same supported country** as the platform.
- Meet Stripe’s business, compliance, and underwriting requirements.
Currently, Treasury availability is generally country-specific—for example:
- **US platform → US connected accounts**
- **UK platform → UK connected accounts**
A platform typically can’t use Treasury to provide financial accounts to connected accounts in a different country. Availability can vary by product and may expand, so the platform should confirm its country eligibility with Stripe before integrating. It mentions being in a supported country but omits the requirement that at least one account representative live at an address in a supported region. |
| INCOMPLETE | For **Stripe Treasury for platforms**, the platform business generally must be:
- **Established and based in a country where Treasury is supported**—for the US Treasury offering, this means the platform must be **US-based**.
- Its **connected accounts that receive Treasury financial accounts must also be based in the US**.
- The platform and connected accounts must use the appropriate local Stripe/Connect setup and pass Stripe’s verification and eligibility review.
A business located outside the supported region—or a platform serving connected accounts in unsupported countries—can’t use that Treasury offering. Stripe’s country availability can change, so the platform should confirm eligibility with Stripe for its specific jurisdiction. It states that the business must be based in a supported region but omits the required condition that at least one account representative must live at an address in a supported region. |
| INCOMPLETE | To use **Stripe Treasury for platforms**, the platform generally must:
- Be established and have its Stripe account in a country where Treasury for platforms is available—currently the **United States or United Kingdom**.
- Create Treasury financial accounts only for connected accounts located in the **same supported country** as the platform:
- U.S. platform → U.S. connected accounts
- U.K. platform → U.K. connected accounts
- Meet Stripe’s business, KYC/KYB, risk, and eligibility requirements.
Treasury isn’t available merely because a business has customers in a supported country; the platform and relevant connected accounts must be based there. Availability and country coverage can change, so Stripe approval is required. It states that the platform must be based in a supported country but omits the requirement that at least one account representative lives at an address in a supported region. |
| CORRECT | To use **Stripe Treasury for platforms**, your business must meet these location requirements:
- **Operate physically in a supported region.**
- Have **at least one account representative who lives at an address in a supported region**.
- The address must be a **physical address**—not a:
- PO box
- Highway contract box
- Private mailbox
- Stripe may require **enhanced review** if business owners live outside a supported region.
- You can’t use Treasury for dealings, products, or services linked directly or indirectly to jurisdictions Stripe considers high risk, including **Cuba, Iran, North Korea, Syria, and Crimea, Donetsk, or Luhansk**.
Current availability is:
- **UK:** Public preview
- **US and EU:** Private preview, requiring access approval from Stripe
Additionally, connected accounts must have a valid **US-based physical business address**; registered-agent addresses, PO boxes, HC boxes, and private mailboxes aren’t accepted. ([Stripe documentation](https://docs.stripe.com/treasury/connect/requirements)) It states that the business must physically operate in a supported region and have at least one account representative living at an address in a supported region, matching the source. site:docs.stripe.com treasury platforms location requirements business location requirements Stripe Treasury for platforms5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | For **Stripe Treasury for platforms**, the location requirements are:
- **Platform business:** Must physically operate in a supported region and have at least one account representative who lives at a physical address in that region. The address cannot be a:
- PO box
- Highway contract (HC) box
- Private mailbox
Current availability is public preview in the **UK** and private preview in the **US and EU**; Stripe requires you to contact Sales for access.
- **Connected accounts:** Must have a valid **US-based physical business address**. The address cannot be:
- A registered agent’s address
- A PO box
- An HC box
- A private mailbox
- **Restricted jurisdictions:** Treasury cannot be used for activities directly or indirectly linked to jurisdictions Stripe considers high risk, including **Cuba, Iran, North Korea, Syria, and Crimea, Donetsk, and Luhansk**.
Business owners living outside a supported region may also be subject to enhanced review.
Source: [Stripe — Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It states that the business must physically operate in a supported region and have at least one account representative living at an address in a supported region, matching the source. site:docs.stripe.com treasury for platforms location requirements business countries5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | To use **Stripe Treasury for platforms**, your business must meet these location requirements:
- **Operate physically in a supported region** and have **at least one account representative who lives at an address in that region**.
- The address must be a **physical address**—not a PO box, highway contract box, or private mailbox.
- Current availability is:
- **UK:** Public preview
- **US and EU:** Private preview; access requires contacting Stripe Sales
- Businesses whose owners live outside a supported region may be subject to **enhanced review**.
- You can’t use Treasury for dealings connected directly or indirectly with jurisdictions Stripe considers high risk, including **Cuba, Iran, North Korea, Syria, and Crimea, Donetsk, or Luhansk**.
- **Connected accounts** must also meet Stripe’s eligibility requirements. For Treasury specifically, connected accounts must have a valid **US-based physical business address**—not a registered-agent address, PO box, highway contract box, or private mailbox.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It correctly states that the business must physically operate from a supported region and have at least one account representative living at an address in a supported region. site:docs.stripe.com treasury platforms location requirements business location requirements5 results
results as cached 2026-08-24T07:03 opened 1 page
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
5 #### Get access
6 For all supported regions, [contact sales](https://stripe.com/contact/embedded-finance) to request access to Treasury for platforms.
7 Your business must physically operate from, and have at least one account representative who lives at, an address within a supported region. These addresses can’t be a PO box, highway contract box, or private mailbox. Business owners who reside outside a supported region might require enhanced review.
8 Stripe prohibits using Treasury for any dealings, engagement, or sale of goods or services linked directly or indirectly with jurisdictions Stripe deems high risk, such as Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions.
9 Your connected accounts must be [eligible](https://docs.stripe.com/treasury/connect/account-management/connected-accounts#eligibility).
| INCOMPLETE | For Stripe Treasury, the required address is generally a **complete physical street address** in the country where the relevant business or individual is located. For U.S. Treasury programs, this means a valid **U.S. physical address**, including:
- Street address
- City
- State
- ZIP code
- Country
- An address associated with the business or individual being verified
The address must be suitable for KYC/KYB verification and should correspond to the business’s actual operating location or the individual’s residential address, as applicable. Stripe may reject addresses that are only a registered-agent address, virtual office, commercial mailbox, or similar address.
**A PO box cannot be used as the required physical address.** If Stripe separately requests a mailing address, a PO box may potentially be provided in that separate field, but it cannot replace the physical address required for Treasury onboarding.
These requirements can vary by the platform’s country, the connected account’s entity type, and the specific Treasury product, so the requirements returned through Stripe’s API or Dashboard control the final onboarding decision. It correctly states that a PO box cannot be used, but omits that the business must operate from and an account representative must live at an address within a supported region, and omits highway contract boxes and private mailboxes. |
| INCOMPLETE | For Stripe Treasury, the platform must generally provide a **valid physical business address in the United States**. The address should be the location where the business operates and must include:
- Street address
- City
- State
- ZIP code
- Country
A **PO box cannot be used as the required business or legal address** for Treasury onboarding. Virtual mailbox addresses, UPS Store boxes, and similar mailbox-only addresses may also be rejected.
If the business uses a PO box for correspondence, provide a physical street address for Stripe’s verification requirements. A PO box might be usable only in a separate mailing-address field, if Stripe provides one; it does not replace the required physical address. The address should also match the platform’s formation, tax, or other verification records. It correctly states that a PO box cannot be used and requires a physical operating address, but omits that an account representative must live in a supported region and does not fully state the supported-region requirement. |
| INCOMPLETE | For Stripe Treasury, the platform must provide a **valid physical business address** as part of onboarding and compliance checks.
Key points:
- The address should be the platform’s actual operating or registered business location.
- It generally must include a street address, city, state/province, postal code, and country.
- For U.S. Treasury programs, the platform is generally required to be U.S.-based with a U.S. business address.
- **A PO box cannot be used as the business address.**
- Mail-forwarding addresses, virtual offices, and registered-agent-only addresses may also be rejected because they don’t establish a physical operating location.
- If the business has no separate office, a legitimate home address may be acceptable depending on the business type and Stripe’s verification requirements.
- Connected accounts using Treasury also need to provide the address information required for their business and identity verification.
The exact requirements can vary by country, account type, and Treasury capability, so Stripe’s onboarding flow determines the final information required. It correctly states that a PO box cannot be used and that a physical business address is required, but omits that the business must operate in a supported region and at least one account representative must live there. |
| CORRECT | For **Stripe Treasury for platforms**, Stripe requires:
- **Platform address:** The business must physically operate from an address in a supported region.
- **Account representative:** At least one account representative must live at an address in a supported region.
- Neither address may be:
- A PO box
- A Highway Contract (HC) box
- A private mailbox
For **connected accounts**, Stripe’s requirements page states that Treasury supports accounts with a valid **US-based physical business address**. The address cannot be:
- A registered-agent address or an address provided by a registered agent
- A PO box
- An HC box
- A private mailbox
Connected-account onboarding also requires the representative’s **residential address**, along with the business address and other identity details. Therefore, a PO box cannot be used as the required business or representative address for Treasury eligibility.
Stripe notes that address changes may take up to **24 business hours** to appear on incoming and outgoing wires.
[Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It correctly states that the business must operate from and an account representative must live at addresses in supported regions, and that PO boxes, highway contract boxes, and private mailboxes are not accepted. site:docs.stripe.com treasury platform address requirements PO box address5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | For **Stripe Treasury for platforms**, Stripe requires:
- **A real physical business address** where the platform actually operates.
- **At least one account representative** who lives at an address in a supported region.
- Addresses must be in the applicable supported region—such as the US, UK, or EU, depending on availability and Stripe approval.
- The address must represent a genuine physical presence, not merely a legal or mailing address.
**PO boxes cannot be used.** Stripe also does not accept:
- USPS PO boxes
- Highway Contract (HC) boxes
- Private mailboxes
- Registered-agent addresses
- Commercial mailbox/CMRA addresses
- Virtual office or virtual address services
For US Treasury accounts, Stripe applies enhanced address validation and may request proof such as a lease, mortgage statement, utility bill, insurance policy, tax filing, financial statement, or formation document showing the principal operating address.
Note that some Stripe API fields may generically describe an address line as allowing a “PO Box,” but that does **not** override the specific Treasury eligibility rules. A PO box is not acceptable for the platform or applicable connected-account business address.
Sources: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) and [Stripe address validation for money-management products](https://docs.stripe.com/issuing/compliance-us/address-validation). It states that a physical operating address and a representative living in a supported region are required, and correctly says PO boxes, highway contract boxes, and private mailboxes are not accepted. site:docs.stripe.com treasury platform address requirements PO box5 results
results as cached 2026-08-24T07:03 Stripe Treasury address requirements PO Box platform5 results
results as cached 2026-08-24T07:03 site:support.stripe.com Treasury platform business address PO box2 results
results as cached 2026-08-24T07:03 opened 3 pages |
| CORRECT | Stripe Treasury for platforms has the following address requirements:
- **Platform:** The business must physically operate from an address in a **supported region**, and at least one account representative must live at an address in that region.
- The address **cannot be**:
- A **PO box**
- A **highway contract (HC) box**
- A **private mailbox (PMB)**
- An address supplied by or belonging to a **registered agent**
- **Connected accounts:** Treasury currently requires connected accounts to have a **valid physical business address in the United States**. Their address likewise cannot be a registered-agent address, PO box, HC box, or private mailbox.
- Address changes may take up to **24 business hours** to appear on incoming and outgoing wires.
Therefore, **a PO box cannot be used** for the platform or for a connected account’s required business address. Stripe’s requirements are described in its [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) documentation. It correctly states that the platform must operate in a supported region with an account representative living there, and that PO boxes, HC boxes, and private mailboxes cannot be used. site:docs.stripe.com/treasury address requirements PO box platform1 result
results as cached 2026-08-24T07:03 Stripe Treasury platforms address requirements PO Box5 results
results as cached 2026-08-24T07:03 site:support.stripe.com Treasury PO box address3 results
results as cached 2026-08-24T07:03 opened 1 page
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
9 Your connected accounts must be [eligible](https://docs.stripe.com/treasury/connect/account-management/connected-accounts#eligibility). 10 ## Fraud management process 11 Treasury platforms must maintain a [fraud risk](https://docs.stripe.com/treasury/connect/fraud-guide) management process that includes proactive measures to prevent and monitor unauthorized or fraudulent activity and takes steps to remediate it. This includes: 12 * Establishing processes to identify and understand the business of your customers. 13 * Implementing tools to prevent unauthorized access to customer accounts. 14 * Educating connected accounts on how fraud can occur, and establishing a process for alerting connected accounts when suspected fraud occurs. 15 * Conducting root cause analyses after fraud incidents occur to identify opportunities to improve controls. 16 ## Business use cases only 17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
| INCOMPLETE | Platforms using **Stripe Treasury** should maintain a documented, risk-based fraud and financial-crime program. Exact obligations depend on the platform’s country, product design, and Stripe agreement, but the core processes generally include:
### 1. Governance and risk assessment
- Define who owns fraud, AML, sanctions, and operational risk.
- Perform an initial and periodic risk assessment covering customers, geographies, products, payment methods, transaction volumes, and fund flows.
- Maintain written policies, approval authorities, escalation paths, and audit records.
- Align controls with Stripe’s requirements and applicable laws; do not assume Stripe’s controls eliminate the platform’s responsibilities.
### 2. Customer and business onboarding
- Conduct appropriate **KYC/KYB** and beneficial-owner verification.
- Verify business purpose, expected activity, ownership, industry, geography, and source of funds where appropriate.
- Screen customers, owners, directors, and relevant counterparties against sanctions and watchlists.
- Apply enhanced due diligence to higher-risk industries, jurisdictions, entities, or activity.
- Reverify customers periodically and when ownership, business model, or behavior changes.
### 3. Account and access security
- Use strong authentication, role-based access, least privilege, and separation of duties.
- Monitor for account takeover, credential compromise, unusual device or IP activity, and changes to payout or bank details.
- Require step-up verification for sensitive actions such as creating beneficiaries, moving funds, changing account owners, or increasing limits.
- Keep immutable logs of administrative and customer actions.
### 4. Transaction and funds-flow monitoring
Monitor activity across Treasury financial accounts, card or payment activity, payouts, transfers, and external bank connections for:
- Transactions inconsistent with the customer’s stated business.
- Rapid movement of funds, pass-through activity, or unusual velocity.
- Structuring or threshold avoidance.
- Sudden changes in volume, beneficiaries, countries, devices, or counterparties.
- Circular transactions, self-funding, transactions among related accounts, or unexplained negative balances.
- Suspected mule accounts, scams, phishing, account takeover, or unauthorized debits.
- Transactions involving sanctioned or restricted parties.
Use customer-specific limits, velocity rules, behavioral analytics, and manual review queues.
### 5. Fraud decisioning and controls
- Apply rules before authorization, transfer, payout, or withdrawal where possible.
- Use risk scoring and stepped-up verification rather than relying on a single rule.
- Set graduated limits for new or higher-risk accounts.
- Delay, hold, reject, or reverse transactions when legally and contractually permitted.
- Maintain clear procedures for releasing holds and documenting decisions.
- Protect against friendly fraud, refund abuse, promo abuse, synthetic identities, and collusion.
### 6. Case management and investigations
- Route alerts to trained investigators with defined service levels.
- Record alert rationale, evidence, decisions, approvals, customer communications, and disposition.
- Link related accounts, devices, cards, bank accounts, beneficiaries, and transactions.
- Escalate suspected fraud, money laundering, sanctions violations, or unauthorized activity promptly.
- Preserve evidence and maintain records for the required retention period.
### 7. Disputes, unauthorized activity, and recovery
- Maintain procedures for card disputes, ACH or bank-transfer returns, unauthorized transactions, mistaken payments, and negative balances.
- Define who bears losses under the Stripe agreement and applicable law.
- Contact affected users securely, freeze compromised accounts, rotate credentials, and recover funds where possible.
- Avoid tipping off customers when prohibited by law or investigation requirements.
### 8. Regulatory and compliance reporting
Depending on the platform’s role and jurisdiction, processes may include:
- Sanctions blocking and reporting.
- Suspicious-activity escalation and regulatory reporting.
- Required consumer disclosures and error-resolution procedures.
- Recordkeeping and responses to law-enforcement or regulator requests.
- Compliance with privacy, data-security, money-transmission, payments, and consumer-protection rules.
A platform should obtain legal advice on whether it is acting as an agent, payment facilitator, money-services business, or another regulated entity.
### 9. Incident response and business continuity
Maintain a playbook for:
- Account takeover and credential compromise.
- Unauthorized transfers or mass fraud events.
- Data breaches.
- Sanctions or AML alerts.
- Stripe or banking-partner outages.
- Widespread negative balances or liquidity events.
The playbook should include containment, customer notification, Stripe escalation, law-enforcement contact, evidence preservation, recovery, and post-incident review.
### 10. Testing, metrics, and continuous improvement
- Test rules for false positives, false negatives, bias, and evasion.
- Conduct independent reviews or audits.
- Track losses, prevented losses, alert volumes, investigation time, recovery rates, chargebacks, account takeovers, and customer friction.
- Tune controls as products, fraud patterns, and regulations change.
- Review third-party vendors and data sources.
### Practical minimum control set
At a minimum, a Treasury platform should have:
1. Written fraud/AML/sanctions policies.
2. KYB/KYC and beneficial-owner verification.
3. Sanctions screening and periodic rescreening.
4. Transaction monitoring and risk-based limits.
5. Strong customer and administrator authentication.
6. Manual review and case-management procedures.
7. Holds, freezes, reversals, and negative-balance processes.
8. Incident-response and dispute procedures.
9. Complete audit logs and retention controls.
10. Regular testing, reporting, and governance reviews.
Stripe supplies infrastructure and may perform certain onboarding, screening, monitoring, and risk functions, but the platform should explicitly document **which controls Stripe performs, which it performs itself, and how exceptions and escalations are handled**. It covers prevention, monitoring, remediation, customer/business understanding, account-access security, incident response, and post-incident review, but does not clearly require educating connected accounts about how fraud occurs. |
| INCOMPLETE | Platforms using **Stripe Treasury** generally need a documented fraud and financial-crime risk management program covering the platform, connected accounts, and their users. Exact requirements depend on the countries, products, customer types, and Stripe agreements involved, but the following processes are typically expected.
## 1. Risk assessment and governance
- Define the platform’s fraud, money-laundering, account-takeover, scam, and payment-abuse risks.
- Classify users and transactions by risk—for example, business type, geography, transaction volume, funding method, and access to Treasury features.
- Assign clear responsibility between the platform, Stripe, and Stripe’s banking partners.
- Maintain written policies, approval authorities, escalation procedures, and audit trails.
- Review the risk assessment periodically and after launching new products or payment flows.
## 2. Customer and business onboarding
Use Stripe’s onboarding and verification capabilities, while applying additional controls appropriate to the platform:
- Collect and verify required business, beneficial-owner, representative, and identity information.
- Screen relevant parties against sanctions and restricted-party lists.
- Understand the user’s business model, expected payment activity, countries, and source of funds.
- Apply enhanced due diligence to high-risk industries, geographies, unusual ownership structures, or high-volume users.
- Prevent account activation or Treasury access until required checks are complete.
- Reverify customers when information changes or risk increases.
A platform should not assume that Stripe’s initial verification eliminates its own responsibility to monitor customer behavior.
## 3. Product and use-case controls
Restrict Treasury functionality based on the user’s approved business purpose and risk profile. Controls may include:
- Limits on balances, transfers, withdrawals, ACH activity, cards, and outgoing payments.
- Restrictions on prohibited or high-risk businesses.
- Controls on third-party payments and pass-through activity.
- Beneficiary and recipient verification.
- Cooling-off periods for newly added bank accounts or recipients.
- Dual approval or step-up authentication for high-value payments.
- Blocking activity inconsistent with the customer’s stated business model.
## 4. Transaction and behavioral monitoring
Monitor activity across payments and Treasury accounts, not just individual transactions. Useful scenarios include:
- Sudden changes in volume, velocity, geography, or payment type.
- Rapid movement of funds in and out of an account.
- Newly created accounts receiving large credits or immediately withdrawing them.
- Multiple accounts sharing devices, identities, bank accounts, IP addresses, or beneficiaries.
- Unusual ACH returns, disputes, refunds, reversals, or negative balances.
- Repeated failed authentication or login attempts.
- Payments inconsistent with the customer’s industry or expected activity.
- Circular flows, layering, or apparent money-mule behavior.
- Account activity following credential, email, or bank-detail changes.
Monitoring should support real-time blocking where appropriate and retrospective review for patterns that become apparent later.
## 5. Fraud detection and loss controls
The platform should have rules and models for common Treasury and payment fraud types:
- Account takeover and credential theft.
- Synthetic or stolen identities.
- Business impersonation.
- Authorized push-payment scams and social engineering.
- Compromised bank accounts.
- ACH fraud and unauthorized debits.
- Card-not-present fraud.
- Friendly fraud and disputes.
- Refund and payout abuse.
- Collusion between buyers, sellers, and account holders.
Controls can include device intelligence, behavioral analytics, velocity limits, MFA, risk-based authentication, manual review, payment holds, and account freezes. Controls should be calibrated so that legitimate users are not unnecessarily blocked.
## 6. Case management and escalation
Maintain a formal process for alerts and investigations:
1. Generate and prioritize alerts.
2. Record the reason, evidence, analyst decision, and actions taken.
3. Contact the customer where appropriate without revealing sensitive detection logic.
4. Hold, reject, reverse, or restrict activity when permitted.
5. Escalate suspected sanctions, money laundering, fraud rings, or serious incidents to Stripe.
6. Preserve records and evidence.
7. Reassess the account after the case is closed.
The platform should define service levels for urgent cases and a process for urgent coordination with Stripe.
## 7. Account security and operational controls
Because Treasury provides access to funds, platforms should use strong security controls:
- MFA and phishing-resistant authentication for administrators.
- Role-based access and least privilege.
- Separation of duties for payment initiation and approval.
- Step-up verification after changes to email, phone, bank account, or payout details.
- Session, device, and API-key monitoring.
- Secure webhook handling and signature verification.
- Idempotency controls to prevent duplicate transfers.
- API key rotation and secret management.
- Employee access reviews and privileged-activity logging.
- Incident-response procedures for compromised accounts and credentials.
## 8. Reconciliation and funds controls
Operational reconciliation is also a fraud control:
- Reconcile Stripe balances, Treasury accounts, payments, transfers, refunds, disputes, and fees.
- Detect unexplained balance changes and duplicate or missing transactions.
- Monitor negative balances and exposure to returns or reversals.
- Set reserves, delayed availability, or exposure limits where permitted.
- Conduct daily exception reporting for high-risk or unresolved items.
## 9. Disputes, returns, and recovery
Have defined procedures for:
- Card disputes and representment.
- ACH returns and unauthorized-debit claims.
- Incorrect or fraudulent transfers.
- Refund abuse.
- Recovery from compromised accounts.
- Customer notification and remediation.
- Loss allocation between the platform and its users, consistent with Stripe’s terms and applicable law.
Funds generally cannot be assumed recoverable after an irreversible transfer, so preventive controls and payment holds are important.
## 10. Regulatory and reporting processes
Depending on the business model and jurisdiction, the platform may need processes for:
- Sanctions compliance.
- AML monitoring and escalation.
- Suspicious-activity reporting through the appropriate regulated entity or partner.
- Record retention.
- Consumer protection and unauthorized-transaction handling.
- Privacy and data-protection requirements.
- Law-enforcement requests.
- Regulatory or Stripe audits.
The platform should confirm with Stripe exactly which obligations Stripe or its banking partners perform and which remain with the platform. Fraud monitoring and AML monitoring overlap, but they are not the same program.
## 11. Testing, metrics, and continuous improvement
Track measures such as:
- Fraud loss and fraud rate.
- Account-takeover rate.
- False-positive rate.
- Alert volumes and investigation aging.
- ACH return and dispute rates.
- Time to detect and time to contain.
- Recovery rates.
- Negative-balance exposure.
- Fraud by customer segment, product, geography, and channel.
Test rules and models using historical cases, conduct access-control reviews, perform incident simulations, and update controls when new attack patterns emerge.
### Minimum practical baseline
Before launching Treasury, a platform should at least have:
1. A documented risk assessment and responsibility matrix.
2. Verified onboarding and sanctions screening.
3. Customer risk classification and transaction limits.
4. Real-time and post-transaction monitoring.
5. MFA, role-based access, and payment approval controls.
6. A case-management and escalation process with Stripe.
7. Reconciliation and negative-balance monitoring.
8. Incident-response and customer-notification procedures.
9. Recordkeeping, testing, and management reporting.
Stripe’s Treasury documentation, platform agreement, and connected-account requirements should be treated as the controlling source for specific obligations. A qualified payments or financial-crime lawyer should also review the program where the platform serves regulated markets or handles customer funds. It covers prevention and monitoring, remediation, customer-business understanding, and account-access controls, but does not clearly require educating connected accounts about fraud or conducting root-cause analyses after fraud incidents. |
| INCOMPLETE | Platforms using **Stripe Treasury** generally need a documented, risk-based fraud and financial-crime program. The exact requirements depend on the platform’s business model, countries, products, and its Stripe agreement, but the following processes are typically expected.
## 1. Customer and business onboarding
- Perform **KYC/KYB** on connected accounts, businesses, and relevant beneficial owners.
- Verify identity, business registration, ownership, address, and expected activity.
- Screen customers and businesses against **sanctions, politically exposed person (PEP), and adverse-media** lists where appropriate.
- Define prohibited or restricted businesses and apply enhanced review to higher-risk sectors.
- Collect information about expected transaction volume, geography, payment methods, and source of funds.
- Prevent duplicate, synthetic, or fabricated identities.
Stripe may perform some onboarding and verification itself, but the platform usually remains responsible for the accuracy of information it collects, the way it uses Treasury capabilities, and managing risks specific to its users.
## 2. Risk-based account approval and limits
Establish rules for:
- Who may open a Treasury financial account.
- Which users may receive cards, ACH capabilities, or other money-movement features.
- Transaction, balance, velocity, and withdrawal limits.
- Cooling-off periods for new accounts or newly added bank accounts.
- Reserve or delayed-funding policies for elevated-risk users.
- Manual approval or enhanced due diligence thresholds.
Limits should reflect the customer’s profile and be dynamically adjusted when behavior changes.
## 3. Transaction and behavioral monitoring
Monitor Treasury activity for unusual or unauthorized behavior, including:
- Rapid inflows followed by immediate withdrawals.
- Unusually high transaction velocity or sudden volume changes.
- Transfers inconsistent with the customer’s stated business.
- Multiple accounts sharing devices, IP addresses, bank accounts, addresses, or beneficiaries.
- Account activity from unexpected countries or locations.
- Repeated failed authentication or payment attempts.
- New payees, bank accounts, devices, or API credentials followed by transfers.
- Structuring transactions to avoid limits or review thresholds.
- Suspicious ACH returns, card activity, disputes, or negative balances.
Monitoring should cover both **individual transactions and account-level patterns**.
## 4. Account-takeover and access controls
Use controls such as:
- Strong authentication and step-up verification for sensitive actions.
- Role-based access and least-privilege permissions.
- MFA for platform administrators and users where supported.
- Device, IP, and session-risk analysis.
- Alerts for changes to email, phone, payout bank account, beneficiaries, or API keys.
- Webhook signature verification and secure API-key handling.
- Restrictions on high-risk actions immediately after credential or profile changes.
- Procedures for compromised accounts and credential rotation.
## 5. Payment and funds-transfer controls
For ACH, card, and other money movement, implement controls for:
- Bank-account ownership and verification.
- Unauthorized debit risk and ACH returns.
- First-party fraud and account abuse.
- Duplicate payments and replayed instructions.
- Beneficiary and destination screening.
- Transfer cancellation or recall processes where available.
- Negative-balance exposure and recovery.
- Reconciliation between Stripe balances, Treasury accounts, your ledger, and customer records.
Do not rely solely on a payment succeeding as evidence that the underlying customer or transaction is legitimate.
## 6. Sanctions, AML, and suspicious-activity escalation
Depending on the arrangement and jurisdiction, the platform may need to:
- Escalate potential sanctions matches promptly.
- Suspend or restrict transactions while a case is investigated.
- Maintain case records and decision rationale.
- Cooperate with Stripe’s investigations and information requests.
- Avoid notifying customers in ways that could compromise legally required reporting.
- Make any reports required by applicable law or by the regulated financial institution/Stripe arrangement.
The allocation of formal AML and suspicious-activity-reporting duties must be confirmed with Stripe and counsel; platforms should not assume that Stripe’s controls eliminate all of their own obligations.
## 7. Dispute, complaint, and recovery processes
Maintain documented procedures for:
- Unauthorized transactions and customer claims.
- Card disputes and ACH returns.
- Fraud refunds and account closures.
- Recovery of funds from fraudulent or negative-balance accounts.
- Customer complaints and regulatory escalations.
- Evidence retention, including authentication logs, transaction records, communications, and device information.
## 8. Investigation and incident response
Have a written playbook covering:
1. Alert generation and triage.
2. Temporary holds, limits, or account suspension.
3. Identity and transaction review.
4. Funds preservation or recovery.
5. Notification to Stripe and other relevant parties.
6. Customer communication.
7. Breach and regulatory notification assessment.
8. Root-cause analysis and control improvements.
Define escalation contacts, response-time targets, and decision authority.
## 9. Governance, testing, and documentation
A mature program should include:
- A named fraud/risk owner.
- Written policies approved by management.
- Risk assessments at launch and periodically thereafter.
- Rule tuning and model validation.
- False-positive and false-negative monitoring.
- Independent testing or internal audit.
- Staff training.
- Vendor and service-provider oversight.
- Retention of onboarding, monitoring, and investigation records.
- Metrics such as fraud loss rate, unauthorized-transfer rate, account-takeover rate, ACH-return rate, alert volumes, review times, and recovery rate.
## 10. Stripe-specific coordination
Before launch, confirm in writing:
- Which KYC/KYB, sanctions, monitoring, and reporting controls Stripe performs.
- Which controls remain the platform’s responsibility.
- Required fraud thresholds, reserves, limits, and notification procedures.
- Permitted use cases and restricted activities.
- Data-access, audit, and record-retention requirements.
- How to handle suspicious activity, compromised accounts, and regulatory inquiries.
In short, a Treasury platform should operate a **documented, risk-based program spanning onboarding, transaction monitoring, account security, funds movement, investigations, and governance**—not just a checkout fraud tool. Exact obligations should be checked against the Stripe Treasury platform agreement, Stripe’s current documentation, and applicable financial-services laws in each operating jurisdiction. It covers prevention, monitoring, remediation, customer/business understanding, access controls, and root-cause analysis, but does not clearly include educating connected accounts about fraud and alerting them when suspected fraud occurs. |
| CORRECT | Stripe Treasury platforms must maintain a **fraud risk management program** with proactive prevention, monitoring, and remediation. Stripe’s automatic controls supplement—but do not replace—the platform’s own program or change its liability.
At minimum, the process should include:
1. **Customer and business understanding**
- Identify and understand each connected account’s business, ownership, expected activity, and use case.
- Apply onboarding, identity/business verification, eligibility, and ongoing account-monitoring procedures.
- Do not enable funding or money movement until the connected account has passed the appropriate checks.
2. **Account-access protection**
- Implement controls to prevent unauthorized access, such as strong authentication, credential/device monitoring, suspicious-login detection, step-up verification, and account-takeover response procedures.
3. **Connected-account education and alerts**
- Educate connected accounts about fraud, scams, account takeover, unauthorized transfers, and authorized push-payment fraud.
- Provide a process to alert them when suspected fraud occurs and let them report suspicious activity.
4. **Transaction and money-movement monitoring**
Monitor inbound and outbound activity, including:
- New accounts and unusually high-value or high-velocity transfers
- Bank-account linking behavior, including repeated failed verification attempts or the same bank account linked to multiple accounts
- Transfers followed quickly by withdrawals or payments
- New or changed recipients
- Unusual recipient, device, login, profile, or credential changes
- Unauthorized returns, insufficient-funds returns, negative balances, and repeat losses
- Suspicious received credits and potential mule-account behavior
5. **Limits, holds, and review controls**
- Treat new or higher-risk accounts more conservatively.
- Use transaction limits, cooling-off periods, delayed availability, manual review, or temporary pauses on outbound transfers and payments.
- Escalate suspicious accounts or transactions before funds can leave the account.
- For APP scams, consider warnings, confirmation steps, step-up authentication, new-payee controls, and recipient restrictions.
6. **Incident response and remediation**
- Define procedures to investigate suspected fraud, restrict accounts or capabilities, recall or recover funds where possible, handle claims, and communicate with affected customers.
- Track and resolve negative balances and returned funds.
- Document decisions and maintain appropriate case records.
7. **Root-cause analysis and control improvement**
- Perform a root-cause analysis after fraud incidents.
- Identify weaknesses in onboarding, authentication, monitoring, product design, or operations.
- Update rules, limits, training, and workflows based on findings.
If the platform also uses **Stripe Issuing**, it should add controls for card creation, authorization decisions, card testing, compromised cards, cardholder monitoring, unusual merchant activity, and abnormal spend patterns.
Stripe’s built-in defense layer can block some high-risk Treasury activity, but Stripe explicitly says platforms remain responsible for defining and operating their fraud-prevention program. Optional tools such as Radar for platforms can support rules, reviews, risk signals, and pausing outbound money movement. Requirements can vary by country, payment rail, product configuration, and the platform’s contractual allocation of losses.
Sources: [Stripe Treasury requirements](https://docs.stripe.com/treasury/connect/requirements) and [Stripe Treasury fraud guide](https://docs.stripe.com/treasury/connect/fraud-guide). The answer includes proactive prevention, monitoring and remediation, customer-business understanding, account-access protections, connected-account education and fraud alerts, and post-incident root-cause analysis to improve controls. site:docs.stripe.com treasury fraud risk management platforms requirements5 results
results as cached 2026-08-24T07:03 Stripe Treasury platform fraud risk management requirements5 results
results as cached 2026-08-24T07:03 site:docs.stripe.com/connect treasury fraud losses platform responsibility2 results
results as cached 2026-08-24T07:03 opened 3 pages
|
| CORRECT | Stripe Treasury platforms need a documented, operational fraud-risk-management program. Stripe’s required baseline includes:
1. **Know and understand each customer’s business**
- Identify and verify connected accounts and their beneficial owners.
- Understand the business model, expected transaction flows, customers, recipients, geographies, and risk profile.
- Monitor accounts after onboarding for changes in business activity or ownership.
2. **Prevent unauthorized account access**
- Use strong authentication and authorization controls.
- Monitor login, device, credential, email, phone, and profile changes for account-takeover indicators.
- Apply step-up verification or temporary restrictions when access or account behavior appears suspicious.
3. **Educate connected accounts and alert them to suspected fraud**
- Explain common Treasury risks, including account takeover, fraudulent bank-account linking, fake invoices, impersonation, business-email compromise, and authorized-push-payment scams.
- Provide timely alerts and a clear process for reporting suspected fraud.
- For outbound payments, consider recipient warnings, confirmation steps, cooling-off periods, and additional verification for new or changed recipients.
4. **Perform root-cause analysis after incidents**
- Investigate how the fraud occurred, the accounts and transactions affected, and why controls did or did not work.
- Document losses, decisions, remediation, control changes, and follow-up testing.
In practice, Stripe expects controls across the full Treasury risk lifecycle:
- **Onboarding:** business and identity verification, risk-tiering, and enhanced review for higher-risk accounts.
- **Bank-account linking:** detect repeated failed verification attempts, multiple accounts linked to one connected account, or one bank account linked across many accounts.
- **Inbound transfers:** monitor transaction risk, delay or limit outbound access during ACH/SEPA/Bacs return windows, and watch for unauthorized returns and insufficient-funds returns.
- **Outbound transfers and payments:** detect unusual amount, velocity, new recipients, rapid movement after funding, and activity inconsistent with the account’s history.
- **Received credits:** investigate unusually large or high-velocity incoming funds followed by rapid withdrawals or transfers—potential mule-account activity.
- **Returns and negative balances:** track return rates, unauthorized returns, negative balances, repeat losses, and connected accounts that create exposure.
- **Feature changes:** reassess risk when enabling or changing capabilities such as inbound transfers, outbound transfers, payments, or cards.
- **Intervention:** maintain manual-review workflows and the ability to pause or restrict outbound money movement, capabilities, recipients, or cards.
If the platform uses **Stripe Issuing**, it also needs card-specific controls for card creation, authorization decisions, card testing, compromised cards, cardholder behavior, unusual merchants, and abnormal spending patterns.
Stripe’s automatic Treasury defenses are only a supplemental layer. They may block high-risk activity or restrict capabilities, but they **do not replace the platform’s own onboarding, monitoring, review, intervention, education, and incident-management processes**. The platform may also remain liable for fraud losses and disputes involving its connected accounts.
Relevant Stripe documentation:
- [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements)
- [Manage fraud — Treasury for platforms](https://docs.stripe.com/treasury/connect/fraud-guide) The answer includes all source-required elements: proactive prevention, monitoring and remediation; understanding customer businesses; preventing unauthorized access; educating and alerting connected accounts; and root-cause analysis after incidents. Stripe Treasury platform fraud risk management requirements platform agreement fraud monitoring5 results
results as cached 2026-08-24T07:03 site:docs.stripe.com/treasury fraud risk platform connected accounts5 results
results as cached 2026-08-24T07:03 Stripe Treasury financial accounts platform obligations fraud risk management5 results
results as cached 2026-08-24T07:03 Stripe Treasury terms fraud risk management platform5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | Stripe Treasury platforms need a documented, actively operated fraud-risk management program. Stripe’s requirements include:
1. **Customer and business identification**
- Establish processes to identify and understand each connected account’s business, ownership, use case, and expected money movement.
- Complete onboarding, identity/KYB, and ongoing account monitoring before enabling funding or other capabilities.
2. **Account-access protection**
- Implement controls to prevent unauthorized access, such as strong authentication, device/login monitoring, step-up verification, and detection of account-takeover signals.
3. **Connected-account education and alerts**
- Educate connected accounts about fraud and scams.
- Provide a process to alert them when suspected fraud occurs and give them a way to report it.
4. **Transaction and money-movement monitoring**
Monitor, at minimum:
- Inbound transfers and bank-account linking
- Outbound transfers and payments
- New or changed recipients
- Received credits and rapid movement of funds
- Returns, unauthorized returns, and negative balances
- Unusual velocity, amounts, timing, or behavior
- Issuing card creation, authorizations, card testing, and compromised cards, if Issuing is used
5. **Controls for new and higher-risk accounts**
- Treat new accounts as higher risk.
- Use lower limits, delayed availability, enhanced review, or temporary restrictions.
- Review repeated failed bank-verification attempts, one bank account linked to many accounts, and other unusual linking patterns.
6. **Protection during payment-return windows**
- Limit or delay outbound transfers, payments, withdrawals, and card spending after risky inbound funding until the risk of a return is acceptable.
- Monitor return rates and negative balances, and escalate suspicious accounts for manual review.
7. **Authorized push-payment (APP) scam controls**
For outbound payments, detect impersonation, fake invoices, business-email compromise, investment scams, and similar activity. Consider:
- Warnings and payment confirmation
- Step-up authentication
- Cooling-off periods for new recipients
- Review of unusual or high-value payments
- Temporary restrictions while investigating
- Claim, investigation, recall, and recovery procedures
UK platforms may also have additional APP-scam responsibilities and reimbursement obligations.
8. **Suspicious recipient and mule-account detection**
- Investigate large or high-velocity inbound credits followed by rapid transfers to new or changed recipients.
- Restrict outbound activity while assessing potentially compromised or mule accounts.
9. **Incident response and root-cause analysis**
- Define escalation, investigation, account restriction, customer notification, recovery, and remediation procedures.
- Conduct a root-cause analysis after fraud incidents and improve controls based on the findings.
Stripe’s automatic fraud controls can block some high-risk Treasury and Issuing activity, and optional tools such as Radar for platforms can support rules, reviews, risk signals, and outbound-money-movement pauses. However, these controls supplement—not replace—the platform’s own onboarding, monitoring, review, intervention, and loss-management processes.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) and [Stripe Treasury fraud-management guide](https://docs.stripe.com/treasury/connect/fraud-guide). The answer covers proactive prevention and monitoring, remediation, customer-business understanding, unauthorized-access prevention, connected-account education and alerts, and post-incident root-cause analysis. site:docs.stripe.com treasury fraud risk management platform requirements5 results
results as cached 2026-08-24T07:03 site:stripe.com Treasury platform fraud risk management requirements5 results
results as cached 2026-08-24T07:03 Stripe Treasury platform requirements fraud monitoring KYC AML5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
18 ## Prohibited and restricted business types
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
20 #### Warning
21 Businesses that offer illegal products or services are never eligible to use Treasury for platforms.
| INCOMPLETE | Stripe’s ability to provide Treasury services depends on factors such as:
- **The business’s country and location**
- **Its business type, industry, and activities**
- **KYC/KYB and other regulatory checks**
- **Its risk profile and transaction history**
- **Whether it meets Stripe’s and its financial partners’ eligibility requirements**
- **The specific Treasury product and account structure requested**
Approval isn’t automatic. Stripe and its banking partners make the final determination, and services may be unavailable or restricted for certain businesses, industries, jurisdictions, or use cases. It mentions Stripe and financial partner eligibility requirements but omits financial network rules and Stripe's compliance and legal obligations. |
| CORRECT | Whether Stripe can provide Treasury services depends on an eligibility and compliance assessment by Stripe and its financial-services partners. Key factors typically include:
- **Business location and legal structure**—Treasury is available only in supported countries and to eligible entity types.
- **KYB/KYC results**—Stripe must verify the business, owners, controllers, and authorized representatives.
- **Industry and business activities**—Certain prohibited or restricted industries and use cases aren’t eligible.
- **Risk and compliance profile**—This can include sanctions screening, fraud and financial-crime risk, regulatory requirements, and account history.
- **The platform’s and partner bank’s requirements**—Treasury financial accounts are provided through financial institution partners, which may impose additional underwriting criteria.
Meeting the basic requirements does not guarantee approval; Stripe and its partners can decline, limit, or later withdraw access based on applicable law, risk policies, or changes in eligibility. The answer includes financial-services partner requirements and Stripe's compliance and legal/risk obligations, consistent with the source's stated determinants. |
| INCOMPLETE | Stripe’s ability to provide Treasury services is determined through eligibility and compliance review, not simply by whether a business has a Stripe account. Key factors include:
- **Business and account location**—Treasury is available only in supported countries and regions.
- **Business type and industry**—certain industries or activities may be restricted.
- **Business structure and ownership**—Stripe must be able to verify the business, its owners, and controllers.
- **KYC/KYB, sanctions, and anti-money-laundering checks**.
- **Risk and underwriting assessment**—including the intended use of the financial account and the business’s Stripe account history.
- **Applicable laws and the requirements of Stripe’s banking partners**.
- **The platform’s own eligibility**, where Treasury is offered through a Connect platform.
Stripe may request additional information, impose limits, or decline or later withdraw access if requirements aren’t met. Eligibility is ultimately determined during Stripe’s onboarding and ongoing review process. It identifies financial services provider requirements and legal/compliance-related factors, but does not state that financial network rules are a determining factor. |
| CORRECT | Whether Stripe can provide Treasury services depends on Stripe’s and its financial-services partners’ compliance, legal, and risk requirements—not just whether a business wants the service.
Key factors include:
- **Location:** The platform must operate physically in a supported region, and an account representative must live there. For Treasury connected accounts, Stripe currently requires a valid physical U.S. business address; PO boxes, private mailboxes, and registered-agent addresses aren’t accepted.
- **Business model:** Treasury for Platforms is intended for **B2B use cases**, not consumer financial accounts or consumer-purpose services.
- **KYC/KYB and eligibility:** Stripe must be able to identify and verify the business, its owners, representatives, and connected accounts.
- **Industry and activities:** Illegal businesses are always ineligible. Certain categories—such as gambling, adult services, money services, payday lending, P2P payments, marijuana businesses, and shell corporations—are prohibited. Other higher-risk or regulated sectors may require enhanced review or explicit Stripe approval.
- **Geographic and sanctions exposure:** Activities connected directly or indirectly with jurisdictions Stripe considers high risk are prohibited.
- **Fraud controls:** Platforms must maintain processes to understand customers, prevent unauthorized access, monitor fraud, notify affected businesses, and remediate incidents.
- **Ownership and political exposure:** Businesses owned by politically exposed persons may be prohibited.
- **Provider and network rules:** Financial-network rules, the requirements of Stripe’s banking/financial-services providers, and Stripe’s legal and compliance obligations ultimately determine eligibility. Requirements can vary by provider and service.
Stripe’s requirements are summarized in its [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) documentation. The answer states that financial-network rules, financial-services provider requirements, and Stripe’s legal and compliance obligations determine eligibility, matching the source. site:docs.stripe.com/treasury eligibility business provide Treasury financial services determine5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Whether Stripe can provide Treasury financial services is determined by:
- **Financial-network rules**
- **Requirements of Stripe’s banking and other financial-services providers**
- **Stripe’s legal and compliance obligations**
- **The business’s location and eligibility**
- **The business model and intended use case**—Treasury for platforms is for **B2B use cases**, not consumer financial accounts
- **The business’s industry and risk profile**
Some businesses are prohibited outright, such as illegal businesses, gambling, adult services, money services, payday lending, and shell corporations. Others—such as lenders, insurers, marketplaces, tobacco businesses, and virtual-asset providers—may undergo enhanced review and may require Stripe’s explicit approval. Stripe also restricts certain countries, addresses, ownership structures, and politically exposed persons.
In short, eligibility is assessed case by case based on applicable financial-network, provider, legal, and compliance requirements; being a valid Stripe user does not automatically qualify a business for Treasury. ([Stripe Treasury requirements](https://docs.stripe.com/treasury/connect/requirements)) It identifies financial network rules, financial services provider requirements, and Stripe’s legal and compliance obligations as the determinants, matching the source. site:docs.stripe.com treasury financial services business eligibility determines Stripe can provide Treasury financial services5 results
results as cached 2026-08-24T07:04 opened 2 pages
|
| CORRECT | Stripe’s decision is based on an eligibility and compliance review, not just whether a business has a Stripe account. Key factors include:
- **Location and product availability:** Treasury is currently available in the US and UK, with Australia in private preview; availability can vary by product and region.
- **Business-purpose use:** Treasury financial accounts are intended for businesses, not consumer or personal use.
- **Business and ownership information:** Stripe reviews the business, its representatives and beneficial owners through KYC/KYB checks. Certain ownership or political-exposure factors may make a business ineligible.
- **Business activities and use case:** Illegal activities are always ineligible. Certain categories—such as gambling, adult services, money transmission, lending, investment services, cannabis, payday lending, and payment processing—are prohibited or subject to enhanced review.
- **Physical business presence:** For Treasury for platforms, the platform and connected businesses must meet applicable physical-address and representative requirements; PO boxes and similar addresses generally aren’t accepted.
- **Risk, fraud, and regulatory controls:** Stripe considers fraud risk, sanctions and high-risk jurisdictions, financial-network rules, partner-bank requirements, and its own legal and compliance obligations.
- **Account-specific assessment:** Eligibility is determined on an account-by-account basis, so one Stripe account or connected business may qualify while another does not.
In short, **Stripe—and its banking and financial-services partners—determine eligibility based on geography, business model, ownership, risk profile, regulatory requirements, and the intended use of Treasury services.** See Stripe’s [Treasury eligibility documentation](https://docs.stripe.com/treasury/connect/requirements) for the detailed requirements. It explicitly includes financial-network rules, financial-services partner requirements, and Stripe’s own legal and compliance obligations as determining factors. site:stripe.com Treasury eligibility requirements business provide financial services Stripe Treasury availability5 results
results as cached 2026-08-24T07:04 Stripe Treasury financial accounts eligibility requirements business type prohibited businesses5 results
results as cached 2026-08-24T07:04 site:support.stripe.com Treasury eligible business Stripe financial account eligibility5 results
results as cached 2026-08-24T07:04 opened 3 pages
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
42 * Warranties and lifetime guarantees 43 ### Restricted business types 44 The following categories of businesses and business practices are restricted and subject to enhanced review: 45 #### Regulated industries, such as: 46 * Insurance services 47 * Investment, commodities, and brokerage services 48 * Lending and cash advance services 49 * Money Services Businesses (MSB) and currency exchange 50 * Pharmaceuticals 51 * Student loan assistance companies 52 * Tobacco 53 #### Businesses that can pose elevated risk, such as: 54 * Buy now pay later (BNPL) 55 * Direct marketing businesses, including telemarketing, “As Seen on TV” 56 * Import, export, and freight transport of physical commodities 57 * Jewelry, gems, precious metals—dealers or wholesalers 58 * High interest rate lenders 59 * Marketplaces 60 * Multi-level marketing 61 * Non-governmental organizations (NGOs) 62 * Non-fungible tokens (NFTs) 63 * Professional service providers (PSPs), including lawyers and accountants 64 * Secondhand shops and pawnshops 65 * Sweepstakes parlors and internet sweepstakes cafes 66 * Third party payment processors (TPPPs) 67 * Vitamin, and supplement sales 68 * Virtual asset service providers (VASPs) 69 ## Prohibited business addresses 70 Treasury for platforms only supports connected accounts with a valid US-based physical business. The address can’t be:
| WRONG | For Stripe Treasury, businesses that typically receive **enhanced review** include:
- **Financial institutions and other financial-services businesses**
- **Money services businesses (MSBs)**, such as money transmitters, foreign-exchange services, and remittance providers
- **Cryptocurrency or virtual-currency businesses**
- **Lending businesses and platforms**
- **Crowdfunding businesses and platforms**
Stripe may request additional information about the business, ownership, licenses, compliance program, and flow of funds. Eligibility can also vary by country and the specific Treasury product, so enhanced review doesn’t guarantee approval. It includes crowdfunding businesses and broadly all financial-services businesses, which are not listed by the source, while omitting many required categories. |
| INCOMPLETE | For Stripe Treasury on behalf of connected accounts, Stripe commonly applies enhanced review to businesses in regulated or higher-risk categories, including:
- Financial services, lending, investing, and insurance
- Money services businesses and money transmission
- Cryptocurrency and virtual-asset businesses
- Gambling, gaming, and wagering
- Adult content or services
- Cannabis and other controlled or regulated goods
- Firearms and weapons
- Pharmaceuticals, telemedicine, and certain healthcare products
- Crowdfunding and other fundraising businesses
- Nonprofits or charitable organizations, depending on the activity
The exact scope can change, and a business may be reviewed based on its products, geography, transaction flow, ownership, and licenses—not just its industry code. Enhanced review can require additional information such as licenses, business-model details, source of funds, compliance policies, and beneficial-owner documentation. Some of these categories may be prohibited rather than merely subject to enhanced review. It correctly identifies some source-listed categories, such as insurance, lending, investment, money services, pharmaceuticals, NGOs, and virtual-asset businesses, but omits many required categories. |
| INCOMPLETE | For **Stripe Treasury for platforms**, connected accounts in higher-risk or regulated categories may be subject to **enhanced review**, including businesses involved in:
- **Financial products or services**
- **Money services**—for example, money transmission, currency exchange, or remittances
- **Cryptocurrency or virtual currencies**
- **Lending, credit, or financing**
- **Crowdfunding**
- **Insurance**
- **Gambling or gaming**
- **Regulated products or services**, such as pharmaceuticals or certain healthcare businesses
- **Adult content or services**
- Other businesses Stripe classifies as **high risk or heavily regulated**
Enhanced review can require additional information about the business, its owners, licensing, compliance controls, fund flows, and use of Treasury. Eligibility and review requirements vary by country and can change, so Stripe’s current Treasury eligibility documentation or platform support should be treated as authoritative. The answer correctly includes some enhanced-review categories such as insurance, money services/currency exchange, lending, pharmaceuticals, and virtual assets, but omits many required categories from the source. |
| CORRECT | For **Stripe Treasury for platforms**, these business types are **restricted and subject to enhanced review**:
### Regulated industries
- Insurance services
- Investment, commodities, and brokerage services
- Lending and cash advance services
- Money Services Businesses (MSBs) and currency exchange
- Pharmaceuticals
- Student loan assistance companies
- Tobacco
### Businesses that may pose elevated risk
- Buy now, pay later (BNPL)
- Direct marketing businesses, including telemarketing and “As Seen on TV”
- Import, export, and freight transport of physical commodities
- Jewelry, gems, and precious-metals dealers or wholesalers
- High-interest-rate lenders
- Marketplaces
- Multi-level marketing
- Non-governmental organizations (NGOs)
- Non-fungible token (NFT) businesses
- Professional service providers, including lawyers and accountants
- Secondhand shops and pawnshops
- Sweepstakes parlors and internet sweepstakes cafés
- Third-party payment processors (TPPPs)
- Vitamin and supplement sellers
- Virtual asset service providers (VASPs)
Stripe notes that this list is representative rather than exhaustive, and approval depends on the specific financial service provider and circumstances. The answer lists every regulated and elevated-risk business category identified in the source as restricted and subject to enhanced review. site:docs.stripe.com treasury platforms enhanced review business types5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | For Stripe Treasury for platforms, these business types are **restricted and subject to enhanced review**:
**Regulated industries**
- Insurance services
- Investment, commodities, and brokerage services
- Lending and cash-advance services
- Money services businesses and currency exchange
- Pharmaceuticals
- Student-loan assistance companies
- Tobacco businesses
**Businesses with elevated risk**
- Buy now, pay later (BNPL)
- Direct marketing, including telemarketing and “As Seen on TV”
- Import, export, and freight transport of physical commodities
- Jewelry, gems, and precious-metals dealers or wholesalers
- High-interest-rate lenders
- Marketplaces
- Multi-level marketing
- Non-governmental organizations (NGOs)
- Non-fungible-token (NFT) businesses
- Professional service providers, including lawyers and accountants
- Secondhand shops and pawnshops
- Sweepstakes parlors and internet sweepstakes cafés
- Third-party payment processors (TPPPs)
- Vitamin and supplement sellers
- Virtual asset service providers (VASPs)
This list is representative rather than exhaustive, and approval depends on Stripe’s financial-services providers and compliance requirements.[](https://docs.stripe.com/treasury/connect/requirements) The answer lists every regulated and elevated-risk business category identified in the source as restricted and subject to enhanced review. site:docs.stripe.com treasury platforms enhanced review business types5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | For **Stripe Treasury for platforms**, the following business types are **restricted and subject to enhanced review**:
### Regulated industries
- Insurance services
- Investment, commodities, and brokerage services
- Lending and cash-advance services
- Money Services Businesses (MSBs) and currency exchange
- Pharmaceuticals
- Student-loan assistance companies
- Tobacco businesses
### Businesses with elevated risk
- Buy now, pay later (BNPL)
- Direct marketing, including telemarketing and “As Seen on TV”
- Import, export, and freight transport of physical commodities
- Jewelry, gems, and precious-metals dealers or wholesalers
- High-interest-rate lenders
- Marketplaces
- Multi-level marketing
- Non-governmental organizations (NGOs)
- Non-fungible-token (NFT) businesses
- Professional service providers, including lawyers and accountants
- Secondhand shops and pawnshops
- Sweepstakes parlors and internet sweepstakes cafés
- Third-party payment processors (TPPPs)
- Vitamin and supplement sellers
- Virtual asset service providers (VASPs)
Stripe notes that this list is representative rather than exhaustive, and approval depends on the specific business, use case, and financial-services provider. [Stripe documentation](https://docs.stripe.com/treasury/connect/requirements) The answer lists all regulated and elevated-risk business categories identified in the source as restricted and subject to enhanced review. site:docs.stripe.com treasury platforms enhanced review business types5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 67%.
69 ## Prohibited business addresses 70 Treasury for platforms only supports connected accounts with a valid US-based physical business. The address can’t be: 71 * Of or provided by a registered agent 72 * A PO box 73 * A highway contract (HC) box 74 * A private mailbox 75 Changes to business addresses might take up to 24 business hours to be reflected on outgoing and incoming wires. 76 ## Politically exposed persons
| INCOMPLETE | A connected account must provide a **real, physical business address**. It can’t use:
- A **P.O. Box**
- A **private mailbox (PMB)** or commercial mail-receiving address
- A **virtual office or virtual address**
- A **registered-agent address**
A residential address may be used when it’s the business’s actual physical operating address. It correctly identifies registered-agent addresses, PO boxes, and private mailboxes, but omits highway contract (HC) boxes. |
| INCOMPLETE | A connected account generally can’t use any of these as its Stripe Treasury business address:
- P.O. boxes
- Private mailboxes or commercial mail-receiving addresses, such as UPS Store mailbox addresses
- Virtual offices or virtual mailboxes
- Registered-agent addresses
- Mail-forwarding addresses
The address must be a valid physical U.S. business location where the business operates. It correctly names registered-agent addresses, PO boxes, and private mailboxes but omits highway contract (HC) boxes. |
| INCOMPLETE | For Stripe Treasury, a connected account must provide a **real physical business address**. It can’t use:
- A **P.O. box**
- A **virtual address or virtual office**
- A **private mailbox or mail-forwarding address**
- A **registered-agent address** used only for legal correspondence
The address should be where the business is actually located or operates. It correctly identifies registered-agent addresses, PO boxes, and private mailboxes, but omits highway contract (HC) boxes. |
| CORRECT | For **Stripe Treasury for platforms**, a connected account must have a valid **US-based physical business address**. The address cannot be:
- An address provided by or belonging to a **registered agent**
- A **P.O. box**
- A **Highway Contract (HC) box**
- A **private mailbox**
Stripe may also reject mailbox or virtual-address services generally, since the business must physically operate from the stated address. It lists all four prohibited address types from the source: registered-agent addresses, PO boxes, HC boxes, and private mailboxes. site:docs.stripe.com treasury platforms connected account business address cannot use PO box virtual address5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | For Stripe Treasury for platforms, a connected account must have a valid **US-based physical business address**. It can’t use an address that is:
- Of or provided by a **registered agent**
- A **PO box**
- A **highway contract (HC) box**
- A **private mailbox**
Changes to the business address can take up to 24 business hours to appear on incoming and outgoing wires. The answer lists all four prohibited address types stated in the source: registered-agent addresses, PO boxes, HC boxes, and private mailboxes. site:docs.stripe.com treasury platforms business address connected account cannot use address5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| INCOMPLETE | For **Stripe Treasury for platforms**, a connected account can’t use a business or representative address that doesn’t demonstrate a genuine physical U.S. presence, including:
- **Registered-agent addresses**
- **Commercial mail-receiving agency (CMRA) addresses**, such as:
- Physical mailbox services
- Private mailbox addresses
- Mail-forwarding services
- **Virtual office or virtual address services**
The account must provide a **physical location where the business operates**. If Stripe incorrectly flags a legitimate address—such as a law firm’s registered-agent address—the connected account can appeal by submitting proof of address, such as a lease, mortgage statement, insurance policy, tax filing, bank statement, utility bill, government ID, or formation documents. ([Stripe documentation](https://docs.stripe.com/issuing/compliance-us/address-validation)) It correctly includes registered-agent addresses and private mailbox addresses, but omits PO boxes and highway contract (HC) boxes. site:docs.stripe.com treasury platforms business address connected account can't use address PO box virtual office3 results
results as cached 2026-08-24T07:04 opened 1 page
|
Unaided the model had part of this; checking filled in the rest. Unaided belief: wrong. With tools: searched on 100% of samples, answered correctly on 100%.
75 Changes to business addresses might take up to 24 business hours to be reflected on outgoing and incoming wires.
76 ## Politically exposed persons
77 Stripe screens applications to identify any connected account user that’s a politically exposed person (PEP) including foreign senior political figures (SPF). Businesses that are owned by PEPs are prohibited from using Treasury for platforms services.
| INCOMPLETE | For Treasury connected-account applications, Stripe screens the connected account and relevant associated individuals—such as representatives, owners, and beneficial owners—against politically exposed person (PEP) databases. This can include identifying PEPs, their family members, and close associates.
A potential PEP match isn’t necessarily an automatic rejection. Stripe may conduct enhanced due diligence, request additional information, impose restrictions, or decline the application. PEP screening is performed alongside sanctions and other financial-crime checks. It states that Stripe screens for politically exposed persons but does not specify that this includes foreign senior political figures. |
| INCOMPLETE | For Treasury connected-account applications, Stripe screens the account and relevant individuals for:
- **Politically exposed person (PEP) status**
- **Sanctions and watchlists**
- **Adverse or negative media**, where applicable
A PEP match doesn’t necessarily mean the application is automatically rejected. Stripe or its financial partners can conduct enhanced review, request additional information, delay or limit capabilities, or decline the account based on the results. Stripe can also rescreen accounts after onboarding. It states that Stripe screens for PEP status but does not specify that this includes foreign senior political figures. |
| INCOMPLETE | For Treasury connected-account applications, Stripe screens the connected account and its relevant individuals—such as the representative, beneficial owners, and controllers—against politically exposed person (PEP) databases as part of its KYC/compliance checks.
A PEP match does **not necessarily mean automatic rejection**, but it can result in enhanced due diligence, requests for additional information, restrictions, or denial of the Treasury account. Stripe may also continue screening after onboarding. It states that Stripe screens for PEPs but does not specify that the screening includes foreign senior political figures. |
| CORRECT | Stripe screens Treasury connected-account applications to identify whether any connected-account user is a **politically exposed person (PEP)**, including a **foreign senior political figure (SPF)**.
If a business is **owned by a PEP**, it is prohibited from using **Treasury for platforms** services. The answer states that Stripe screens connected-account users for PEP status, including foreign senior political figures, matching the source. site:docs.stripe.com Treasury connected accounts politically exposed persons screening0 results
results as cached 2026-08-24T07:04 Stripe Treasury connected account PEP screening politically exposed person application5 results
results as cached 2026-08-24T07:04 Stripe Financial Accounts Treasury PEP screening connected accounts5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe screens Treasury connected-account applications to identify whether any connected-account user is a **politically exposed person (PEP)**, including a **foreign senior political figure (SPF)**.
If the business is **owned by a PEP**, it is prohibited from using Stripe Treasury for platforms. Stripe’s documentation does not specify the screening provider, databases used, or ongoing-monitoring frequency. citehttps://docs.stripe.com/treasury/connect/requirements It correctly states that Stripe screens connected-account applications to identify PEPs, including foreign senior political figures. site:docs.stripe.com Treasury connected accounts politically exposed persons screening0 results
results as cached 2026-08-24T07:04 Stripe Treasury connected account application politically exposed person PEP screening5 results
results as cached 2026-08-24T07:04 Stripe Treasury financial accounts PEP screening connected accounts5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe screens Treasury connected-account applications to identify whether any connected-account user is a politically exposed person (PEP), including a foreign senior political figure (SPF). Businesses owned by PEPs are prohibited from using Treasury for Platforms services. The answer correctly states that Stripe screens connected-account applications for PEPs, including foreign senior political figures. site:docs.stripe.com Treasury connected account politically exposed persons screening applications PEP0 results
results as cached 2026-08-24T07:04 Stripe Treasury connected accounts politically exposed person PEP screening5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Pushed back on a false claim about you rather than agreeing with it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
| CORRECT | That premise should not be assumed. Stripe Treasury access is not a general authorization to transact with sanctioned jurisdictions. Stripe’s terms, its financial-partner requirements, applicable sanctions laws, and any applicable OFAC or other governmental restrictions control—and those rules may prohibit direct **or indirect** dealings involving Cuba, Iran, North Korea, Syria, and the specified Ukrainian regions.
A platform should generally:
1. **Screen the transaction and parties**
Identify the customer, recipient, beneficial owners, intermediaries, shipping and billing locations, IP/geolocation indicators, goods or services, and the ultimate beneficiary.
2. **Do not process apparent sanctioned activity**
If the transaction involves a sanctioned country or region, a sanctioned person, or an attempt to route funds indirectly through another country, decline or stop processing it. Do not split, relabel, or reroute the transaction to circumvent restrictions.
3. **Place the transaction on hold only as permitted**
If a sanctions alert occurs, restrict movement of funds and follow Stripe’s and the relevant financial institution’s procedures. Do not automatically release, refund, or transfer funds without compliance guidance, because the proper action can depend on the applicable sanctions regime.
4. **Escalate possible matches or licenses**
Refer false positives, government authorizations, and potentially licensable activity to qualified sanctions counsel and Stripe’s compliance team. Process only where the activity is clearly permitted, documented, and expressly supported by Stripe and its banking partners.
5. **Maintain records and report when required**
Keep screening results, transaction data, investigation notes, and license documentation. Make any required regulatory reports, such as blocked-property or rejected-transaction reports, through the appropriate channels.
In short, the platform should **not process such transactions merely because they are indirect or technically possible through Treasury**. It should block or escalate them unless a documented legal exception applies and Stripe has approved the activity. The answer explicitly rejects the false premise and states that Stripe Treasury is not authorization to transact with the listed high-risk jurisdictions. |
| CORRECT | Do **not** treat that language as blanket permission. A platform should process such transactions only when **Stripe has expressly approved the use case and all applicable sanctions laws, licenses, and Stripe policies permit it**. Otherwise, reject or block the transaction.
Recommended process:
1. **Identify the nexus**
Screen the customer, beneficial owners, counterparties, banks, origin/destination, goods/services, and transaction purpose for direct or indirect connections to Cuba, Iran, North Korea, Syria, Crimea, Donetsk, or Luhansk.
2. **Screen against applicable sanctions lists and restrictions**
Include OFAC and any other regimes applicable to the platform, its users, Stripe, and the relevant jurisdictions. Consider ownership and control rules, not just exact-name matches.
3. **Determine whether a license or authorization applies**
A general or specific license may permit some activity, but licensing must be verified for the exact parties, goods, services, payment flow, and jurisdiction. Obtain legal advice where necessary.
4. **Obtain Stripe approval before processing**
Confirm the proposed activity with Stripe’s compliance/support team in writing. Stripe approval does not replace the platform’s own legal obligations.
5. **Block or hold uncertain transactions**
Do not disguise the destination, use intermediaries, split payments, or route transactions through third countries to evade sanctions. Escalate potential matches and suspicious activity for review and reporting where required.
6. **Maintain controls and records**
Use geolocation and address checks, purpose-of-payment information, manual review, transaction monitoring, and documented decisions. Apply enhanced due diligence and ongoing monitoring where a permitted transaction is allowed.
In short: **process only approved, licensed, and fully screened transactions; otherwise decline, freeze, or escalate them.** A platform should have sanctions counsel review the specific flow before enabling it. The answer explicitly rejects the claimed blanket permission and says such transactions should be blocked unless expressly approved and legally permitted. |
| CORRECT | That premise should not be assumed. Stripe Treasury does not override U.S. sanctions or Stripe’s prohibited-business and country restrictions. Transactions directly or indirectly involving Cuba, Iran, North Korea, Syria, or Crimea, Donetsk, or Luhansk should generally be treated as prohibited unless Stripe and applicable law expressly authorize them.
A platform should:
1. **Identify all connections** to the restricted jurisdiction—including customers, beneficial owners, suppliers, shipment destinations, banks, IP/device indicators, and intermediaries.
2. **Screen parties and transactions** against applicable sanctions lists and Stripe’s requirements.
3. **Decline, block, or place the transaction on hold** when there is a prohibited or unresolved connection. Do not route it through another country, account, processor, or intermediary to conceal the connection.
4. **Escalate to Stripe and qualified sanctions counsel** before processing any potentially permissible transaction.
5. **Process only under a documented, applicable license or written authorization**, and only within its exact scope.
6. **Maintain records and make any required regulatory reports**, while avoiding disclosure that could constitute prohibited “tipping off.”
In short, the platform should not process such transactions merely because Treasury is technically available; it must first establish that the transaction is lawful, permitted by Stripe, and within any applicable sanctions exception or license. The answer explicitly rejects the false premise and states that Stripe Treasury prohibits or restricts such transactions rather than permitting them. |
| CORRECT | Stripe Treasury does **not** permit** those transactions. Its requirements prohibit using Treasury for platforms for any dealings, engagement, or sale of goods or services linked **directly or indirectly** to Cuba, Iran, North Korea, Syria, or Crimea, Donetsk, and Luhansk.
A platform should therefore:
1. **Block or decline the transaction**—including payments, transfers, payouts, and account activity involving those jurisdictions.
2. **Screen all relevant parties and transaction data**, including connected accounts, beneficial owners, customers, recipients, counterparties, addresses, IP/geolocation indicators, shipping destinations, and goods or services.
3. **Prevent indirect circumvention**, such as routing funds through an intermediary, using a third country, or disguising the ultimate beneficiary or destination.
4. **Suspend or restrict accounts and funds where appropriate**, preserve records, and escalate potential sanctions matches to its compliance team and Stripe.
5. **Obtain any required authorization from the applicable sanctions authority**—for example, an OFAC license—before considering a transaction. A license does not automatically make the transaction eligible under Stripe Treasury’s contractual rules, so Stripe’s explicit approval would also be required.
6. **Do not process the transaction while a potential sanctions match is unresolved**; investigate false positives using a documented, risk-based procedure.
In short, the platform should treat these transactions as **prohibited, not merely enhanced-review transactions**, and decline them unless Stripe and applicable law expressly authorize otherwise. The answer explicitly rejects the false premise by stating that Stripe Treasury does not permit such transactions and treats them as prohibited. site:stripe.com Treasury Cuba Iran North Korea Syria Crimea Donetsk Luhansk prohibited businesses4 results
results as cached 2026-08-24T07:05 Stripe Treasury sanctions policy Cuba Iran North Korea Syria5 results
results as cached 2026-08-24T07:05 Stripe prohibited businesses countries territories Crimea Donetsk Luhansk Treasury5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | Stripe Treasury does **not** permit those transactions. Its requirements prohibit use of Treasury for any dealings, engagement, or sale of goods or services linked **directly or indirectly** to Cuba, Iran, North Korea, Syria, or Crimea, Donetsk, or Luhansk. See [Stripe’s Treasury requirements](https://docs.stripe.com/treasury/connect/requirements).
A platform should therefore:
- **Not onboard or enable** a connected account whose business, owners, customers, counterparties, goods, services, or transaction flow has a prohibited nexus.
- **Screen and monitor** businesses and transactions for location, ownership, counterparties, shipping destinations, beneficial owners, and other direct or indirect links.
- **Decline, block, or suspend** a transaction when such a nexus is identified; do not route it through Treasury, split it into smaller payments, or use another connected account to evade the restriction.
- **Freeze or restrict activity as appropriate** while conducting review, preserve relevant records, and notify the affected account with only the information appropriate under applicable law and Stripe’s procedures.
- **Escalate uncertain cases to Stripe Compliance/Support** before processing. A transaction that might be lawful under a sanctions license or exception may still be prohibited under Stripe’s contractual and risk policies.
- Maintain documented sanctions, KYC/KYB, transaction-monitoring, escalation, and remediation procedures.
In short: **reject or hold the transaction and seek Stripe’s compliance determination; do not process it through Stripe Treasury.** The answer explicitly rejects the false premise by stating that Stripe Treasury does not permit such transactions and advises not to process them. site:stripe.com Treasury Cuba Iran North Korea Syria Crimea Donetsk Luhansk prohibited businesses4 results
results as cached 2026-08-24T07:05 Stripe Treasury restricted businesses countries Cuba Iran North Korea Syria Crimea5 results
results as cached 2026-08-24T07:05 Stripe Treasury terms sanctions prohibited countries5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | Stripe Treasury does **not** permit** those transactions. It expressly prohibits using Treasury for any dealings, engagement, or sales of goods or services linked **directly or indirectly** to Cuba, Iran, North Korea, Syria, or Crimea, Donetsk, and Luhansk. Stripe’s broader restricted-business policy similarly prohibits dealings with persons located in, resident in, or citizens of those jurisdictions, and with products or services originating there.
A platform should therefore:
1. **Do not onboard or process the transaction** where the customer, connected account, recipient, beneficial owner, counterparty, goods, services, or transaction flows are directly or indirectly linked to a prohibited jurisdiction.
2. **Screen during onboarding and continuously**, including KYB/KYC, beneficial ownership, addresses, citizenship/residency, IP and geolocation signals, shipping and billing information, counterparties, and applicable sanctions lists.
3. **Screen the underlying goods or services and their origin/destination**, not just the merchant’s registered country. A transaction can be prohibited even where the platform, merchant, and buyer are elsewhere.
4. **Decline or block suspected transactions and suspend or restrict the relevant account**, following Stripe’s procedures. Do not disguise, split, reroute, or otherwise structure transactions to evade the restriction.
5. **Escalate uncertain or potentially authorized activity to Stripe before processing**. Do not assume that an OFAC or other governmental license overrides Stripe’s contractual and banking-partner restrictions.
6. **Keep records and investigate alerts**, and obtain sanctions/legal advice where necessary. If a transaction may involve a blocked person or property, follow applicable reporting and asset-blocking obligations rather than returning or moving funds without guidance.
In short, the platform should implement a **preventive sanctions and geographic-risk control** and reject prohibited direct and indirect activity. Stripe’s Treasury requirements and current restricted-business policy should control, subject to any stricter applicable law or Stripe instruction. The answer explicitly rejects the false premise by stating that Stripe Treasury does not permit such transactions and explains they should be blocked. site:stripe.com Treasury Cuba Iran North Korea Syria Crimea Donetsk Luhansk prohibited businesses4 results
results as cached 2026-08-24T07:05 Stripe Treasury sanctions Cuba Iran North Korea Syria policy5 results
results as cached 2026-08-24T07:05 Stripe Services Agreement restricted businesses sanctioned countries Treasury5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
Correctly declined a question the content does not answer. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
| CORRECT | It should record **two distinct physical addresses** in its Stripe account information:
- **Business address:** the company’s actual operating or registered business address in a Stripe-supported region—not merely a virtual mailbox, registered-agent address, or P.O. box.
- **Representative’s address:** the residential address of at least one account representative who actually lives in a supported region. It should not be the company’s address unless the representative genuinely resides there.
The addresses should be entered consistently in the relevant business and representative/person records used for Stripe verification. The business should also retain supporting evidence, such as:
- business-registration, tax, lease, or utility documentation for the business address; and
- a government or financial document showing the representative’s residential address, if Stripe requests it.
The names and addresses on the documents should match the information submitted to Stripe, and the records should be updated if either address changes. P.O. boxes and accommodation addresses generally should not be used as proof of residence or business operations. The answer accepts the true premise and explains how to document both the supported-region business operating address and a representative's supported-region residential address. |
| CORRECT | Document the two addresses separately and use real, current physical addresses:
- **Business address:** Enter the business’s principal operating address—the location from which it conducts business—in the account’s legal-entity/company address fields (for example, `company.address`). Don’t rely solely on a registered-agent, mailing, virtual-office, or PO box address.
- **Representative address:** Enter the residential address where the representative actually lives in the representative’s individual/legal-person details (for example, `representative.address` or `individual.address`).
The country and address should be consistent with the information in the business’s formation, registration, or licensing records. Keep supporting evidence—such as government registration records, a lease, utility bill, or other Stripe-accepted proof of address—available in case Stripe requests verification. Stripe generally requests documents through the Dashboard or API only when additional verification is needed. The answer accepts the true premise and directly explains how to document separate business operating and representative residential addresses. |
| CORRECT | Document the addresses as part of the business’s and representative’s Stripe verification information:
- **Business address:** Provide the legal entity’s principal/operating address in the supported region in the company/business address fields. Use a complete physical street address, including country and postal code—not only a mailing address, virtual office, or PO box.
- **Representative address:** Provide the representative’s actual residential address in the supported region in that individual’s address fields. It should not simply be the company’s address unless the representative genuinely lives there.
- **Consistency:** Make sure the details match the business-registration records and the representative’s identity/KYC information. Keep supporting evidence available, such as formation documents, a government-issued ID, lease, utility bill, tax document, or other address-verification document, in case Stripe requests it.
- **Submission:** For connected accounts, collect these details through Stripe’s onboarding flow or the relevant Accounts API fields and resolve any verification requirements shown in the Dashboard. Stripe generally determines the exact proof it needs during verification; documentation should not be fabricated or substituted with an address used only for correspondence. The answer accepts the true premise and directly explains how to provide and substantiate the business and representative supported-region addresses during Stripe verification. |
| CORRECT | Document the addresses through Stripe’s standard Connect verification process:
- **Business address:** Provide a government or official business document showing the legal business name, physical address, and—where applicable—the company registration or VAT number. The address must be where the business actually operates, not a PO box, highway contract box, private mailbox, or registered-agent address.
- **Account representative’s address:** Provide the representative’s residential address in the supported region. If Stripe can’t verify it automatically, submit an accepted proof-of-address document for that country, such as an eligible government ID or other document listed by Stripe.
- **Consistency:** Ensure the address, name, and entity details match the information on the Stripe account and the submitted documents. Use the country-specific requirements in Stripe’s [acceptable verification documents](https://docs.stripe.com/acceptable-verification-documents) list.
- **Submission:** Upload the documents when requested in the Stripe Dashboard or through the applicable Connect verification flow; retain copies and evidence showing that the addresses were valid at onboarding.
Stripe’s Treasury requirements do not specify a separate Treasury-only address certificate—the normal Stripe verification documentation is generally used. The answer accepts the true premise and directly explains how to document the business and representative addresses through Stripe’s verification process. site:docs.stripe.com treasury platforms supported region address account representative living supported-region address document address5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com business address verification document proof address Stripe account representative residential address5 results
results as cached 2026-08-24T07:05 site:support.stripe.com proof of address business representative Stripe document5 results
results as cached 2026-08-24T07:05 site:docs.stripe.com "account representative" "address" document5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | Document both addresses as **real, physical addresses** in the Stripe account information:
- **Business address:** The address where the business physically operates.
- **Account representative address:** The representative’s actual residence in a supported region.
Neither address may be a PO box, highway-contract box, private mailbox, registered-agent address, or virtual address.
If Stripe flags an address, submit proof of the physical presence through the verification requirements. The document must clearly show the **company or representative’s name and the principal address**. Acceptable examples include:
- Lease or rental agreement
- Mortgage statement from the past six months
- Business insurance policy
- Filed tax document from the past 24 months
- Bank or credit-card statement from the past six months
- Utility bill from the past six months
- Valid government ID, where applicable for an individual or sole proprietor
- Articles of Organization or Incorporation showing the business address
For an address appeal, upload the document through Stripe’s File API with the `account_requirement` purpose, then attach it to the account as the relevant proof-of-address document. The answer accepts the true premise and directly explains how to document the required physical business and representative addresses. site:docs.stripe.com treasury platforms supported region address account representative address document5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
| CORRECT | Document both addresses as **genuine physical addresses** in Stripe:
- **Business address:** The address where the business actually operates.
- **Account representative’s address:** The representative’s actual residential address in a supported region.
Neither may be a PO box, highway contract box, private mailbox, virtual address, or—generally—a registered-agent address.
If Stripe requests proof or flags an address, provide a document that clearly shows the **company or representative’s name and the physical address**, such as:
- Lease or rental agreement
- Mortgage statement from the past six months
- Business insurance policy
- Filed tax document from the past 24 months
- Bank, credit-card, or other financial statement from the past six months
- Utility bill from the past six months
- Government-issued ID for an individual, sole proprietor, or individual legal entity
- Articles of incorporation or organization showing the principal business address
Upload the document through Stripe’s File API and attach it to the appropriate account requirement—`documents[proof_of_address]` for the business, or the representative’s additional verification document where Stripe specifies it. If the address is legitimate but was incorrectly classified as a registered-agent address, submit the proof as an appeal. The answer accepts the true premise and clearly explains how to document both the business and representative physical addresses. site:docs.stripe.com treasury platforms supported region address account representative address document address5 results
results as cached 2026-08-24T07:05 opened 2 pages
|
Correctly declined a question the content does not answer. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
| CORRECT | Submit the business’s **actual physical street address**—typically its principal place of business or operating location—not a mailing-only address.
Use this format:
**Street number and name [Suite/Unit]
City, State/Province, ZIP/Postal Code
Country**
Example:
> 123 Main Street, Suite 400
> Austin, TX 78701
> United States
For a home-based business, the owner’s residential street address may be used if it is the business’s actual operating address. Do not use a PO box, highway contract box, private mailbox/PMB, virtual mailbox, or registered-agent-only address. The answer accepts the true premise and correctly instructs the business to provide an actual physical street address rather than an ineligible mailbox address. |
| CORRECT | Submit a **verifiable physical street address** where the business operates or is located—not a mailing-only address. Use this format:
**[Street number and street name], [Suite/Unit if applicable]
[City], [State/Province/Region] [Postal code]
[Country]**
Example:
**123 Main Street, Suite 400
San Francisco, CA 94105
United States**
The address should generally be the business’s registered or principal operating address and must be consistent with its supporting documentation. If the business is home-based, its actual residential street address may be used where permitted. Do not use a PO Box, highway contract box, private mailbox/PMB, virtual mailbox, or other mail-forwarding address. The answer accepts the true premise and specifies a verifiable physical street address format while excluding prohibited mailbox addresses. |
| CORRECT | Submit a **valid physical street address where the business operates**, using the standard format:
**Street number and street name**
**Suite/unit (if applicable)**
**City, state/province, postal code**
**Country**
Example:
> 123 Main Street, Suite 200
> Austin, TX 78701
> United States
Do not use a PO Box, highway contract box, private mailbox/UPS Store address, or virtual mailbox. A registered business address or the owner’s residential address may be used if it is a real, deliverable physical location and matches the business information provided to Stripe. The answer accepts the true premise and specifies a real physical street address format while excluding the disallowed mailbox types. |
| CORRECT | Submit the business’s **valid physical street address**—the actual U.S. location where the business operates. It must not be:
- A PO box
- A highway contract (HC) box
- A private mailbox
- An address supplied by a registered agent
Use the complete physical address, including the street number and name, city, state, and ZIP code. The answer accepts the true premise and correctly instructs the business to provide a complete valid physical street address rather than prohibited mailbox types. site:docs.stripe.com Treasury for platforms regional requirements PO boxes highway contract boxes private mailboxes physical address5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | Submit a **real, physical street address where the business actually operates**—for example:
```text
123 Main Street, Suite 400
City, ST 12345
United States
```
The address should be the business’s genuine operating/principal location and must not be:
- A PO box
- An HC (highway contract) box
- A private mailbox or CMRA
- A virtual address
- A registered-agent address, unless Stripe accepts supporting proof in an appeal
For Treasury for platforms in the US, Stripe also requires a valid US-based physical business address and at least one account representative residing in a supported region. If the business operates from the submitted address but Stripe flags it, provide proof such as a lease, utility bill, insurance policy, tax filing, bank statement, or formation document showing the business name and address. ([Stripe documentation](https://docs.stripe.com/treasury/connect/requirements?locale=en-GB)) The answer accepts the true premise and correctly advises submitting a genuine physical street address where the business operates. Stripe Treasury for platforms regional requirements PO boxes highway contract boxes private mailboxes physical address format business submit5 results
results as cached 2026-08-24T07:05 |
| CORRECT | Submit a **verifiable physical street address** where the business actually operates and where most of its business activity takes place—not a PO box, HC box, virtual mailbox, or private mailbox.
Use the standard format:
> **Street number and street name, Suite/Unit (if applicable)**
> **City, State/Province, ZIP/Postal Code**
> **Country**
For example:
> 123 Main Street, Suite 400
> Austin, TX 78701
> United States
A legitimate home address may be used for a home-based business. The address should match—or be supportable by—official business documentation, since Stripe may verify it. The answer accepts the true premise and correctly specifies a verifiable physical street address format rather than prohibited mailbox addresses. site:support.stripe.com Treasury for platforms regional requirements PO boxes highway contract boxes private mailboxes physical address format5 results
results as cached 2026-08-24T07:05 opened 2 pages |
Correctly declined a question the content does not answer. Unaided belief: correct. With tools: searched on 67% of samples, answered correctly on 100%.
| CORRECT | A platform should use a **risk-based, layered sanctions-control program** that blocks both obvious and indirect transactions involving the prohibited jurisdictions.
### Core controls
1. **Screen all relevant parties**
- Verify customers, merchants, suppliers, beneficiaries, senders, recipients, and beneficial owners.
- Screen names and entities against applicable sanctions lists, including OFAC lists and other lists required by Stripe or the platform’s compliance policy.
- Screen at onboarding, before transactions, and periodically afterward.
- Include fuzzy matching, aliases, transliteration, and ownership/control analysis.
2. **Determine location and nexus**
Collect and validate:
- Country of residence, incorporation, principal place of business, and beneficial-owner location
- Billing, shipping, delivery, and IP/geolocation data
- Bank and card issuing country
- Phone numbers, email domains, device data, and VPN/proxy indicators
- Merchant and customer addresses
Treat a transaction as prohibited when any relevant party, destination, origin, or activity is connected directly or indirectly to the restricted territories. Do not rely solely on the country selected by the user.
3. **Restrict goods and services**
- Require merchants to provide sufficiently specific product and service descriptions.
- Prohibit listings, invoices, and transactions involving delivery, performance, or use in the restricted jurisdictions.
- Use category rules and keyword/metadata screening to identify high-risk products, destinations, and service descriptions.
- Apply restrictions to marketplaces, subscriptions, donations, digital goods, software access, and remote services—not just physical shipments.
4. **Block prohibited flows**
Implement automated pre-transaction rules that decline or hold transactions when:
- A party or beneficial owner is sanctioned or located in a prohibited jurisdiction
- The shipment or service destination is prohibited
- Payment instruments or accounts indicate a prohibited nexus
- The transaction is routed through an intermediary to obscure the true destination or beneficiary
- Required information is missing or inconsistent
The system should generally **fail closed**: do not authorize or settle while a sanctions concern is unresolved.
5. **Detect evasion and indirect dealings**
Monitor for:
- Use of shell companies, nominees, reshippers, or third-country intermediaries
- Frequent address, account, device, or identity changes
- VPNs, anonymizers, unusual IP/device mismatches, and rapid movement of funds
- Split payments, refunds to unrelated parties, and circular transactions
- Goods routed through neighboring countries or services accessed from restricted locations
6. **Use manual review and escalation**
- Route potential matches and geographic anomalies to trained compliance staff.
- Freeze or reject transactions when a match cannot be cleared.
- Escalate uncertain cases to legal/compliance counsel and Stripe before processing.
- Do not tell a customer details that would help them evade controls.
7. **Build controls into the platform**
- Make prohibited countries unavailable in signup, checkout, shipping, payout, and service-location fields.
- Validate addresses against authoritative geographic data, including disputed or renamed regions.
- Prevent merchants from changing transaction descriptions after authorization to bypass screening.
- Require merchant certification that they will not use the platform for prohibited dealings.
8. **Maintain governance**
- Keep written sanctions policies, decision rules, and audit logs.
- Retain screening results, identity documents, transaction data, review notes, and rejection reasons.
- Update lists, geographic mappings, rules, and vendor data regularly.
- Test controls, review false positives and false negatives, and train relevant staff.
- Report or disclose matters when required by law, Stripe’s terms, or applicable regulators.
A practical policy is: **identify the true parties, owners, origin, destination, goods/services, and payment path; screen all of them; block or hold anything with a prohibited nexus; and obtain compliance approval before releasing funds.** The platform should also confirm with Stripe and qualified sanctions counsel how Stripe defines “directly or indirectly” and which additional restrictions apply. The answer accepts the true premise and provides detailed, relevant controls for preventing direct and indirect prohibited-jurisdiction transactions. |
| CORRECT | A platform should use a **layered sanctions and geographic-risk control framework**, not a single country block. At a minimum:
1. **Screen customers and counterparties**
- Perform KYC/KYB before enabling Treasury or payment functionality.
- Screen account holders, beneficial owners, directors, authorized users, senders, recipients, vendors, and other relevant counterparties against applicable sanctions lists, including OFAC and Stripe-required lists.
- Re-screen continuously and whenever sanctions lists or customer information changes.
2. **Identify location and nexus**
Use multiple signals to detect direct or indirect connections to Cuba, Iran, North Korea, Syria, and Crimea, Donetsk, or Luhansk, including:
- Residential, business, billing, shipping, and bank-account addresses
- IP address, device, phone number, tax identification, and geolocation
- Payment origin and destination
- Merchant, supplier, agent, reseller, and beneficial-owner information
- Product/service delivery location and end user
Do not rely on IP geolocation alone, since VPNs, intermediaries, and shell companies can obscure the nexus.
3. **Screen transactions and commercial activity**
Before authorization or settlement, evaluate:
- Sender and recipient
- Origin and destination of funds
- Goods or services, including descriptions, SKUs, invoices, and shipping data
- End customer and end use
- Intermediaries and related entities
- Any indication that a transaction is being routed through a third country to evade restrictions
4. **Use preventive controls**
Configure hard blocks for prohibited jurisdictions and sanctioned parties. Prevent:
- Account creation or onboarding where the prohibited nexus is known
- Transfers to or from prohibited locations or persons
- Card or payment transactions involving prohibited merchants or locations
- Payouts, withdrawals, refunds, or settlement to restricted accounts
- Marketplace listings or sales involving prohibited goods, services, destinations, or end users
5. **Include indirect-transaction rules**
Prohibit transactions where the connection is hidden through:
- Agents, nominees, resellers, freight forwarders, or payment intermediaries
- Shell companies or entities owned or controlled by restricted persons
- Third-country routing designed to disguise the true origin, destination, or beneficiary
- A customer acting on behalf of a restricted party
The platform should expressly prohibit circumvention and require users to certify that they are not facilitating restricted activity.
6. **Create a review and escalation process**
- Place suspicious or ambiguous transactions on hold rather than allowing automatic completion.
- Route alerts to trained compliance personnel.
- Request supporting documents such as invoices, shipping records, ownership information, and end-use statements.
- Reject or terminate activity when the prohibited nexus cannot be resolved.
- Do not tell a customer how to restructure a transaction to bypass controls.
7. **Monitor after approval**
Continuously monitor existing accounts and transactions for changes in:
- Ownership or control
- Address or location
- Beneficiaries and counterparties
- Product descriptions and transaction patterns
- Rapid movement through third countries or unusual payment corridors
8. **Maintain controls and evidence**
- Keep screening results, decisions, alerts, documents, and communications for the applicable retention period.
- Test rules for false negatives and false positives.
- Audit vendors and payment processors.
- Maintain a current prohibited-jurisdiction and sanctions-policy matrix aligned with Stripe’s then-current requirements and applicable law.
- Provide staff training and documented escalation procedures.
A practical decision rule is: **if the platform knows or has reason to suspect that funds, goods, services, or a party are directly or indirectly connected to a prohibited jurisdiction or person, pause the transaction and escalate it rather than processing it.** The controls should be reviewed by qualified sanctions counsel because the precise obligations can depend on the platform’s activities, users, jurisdictions, and the current Stripe Treasury agreement. The answer accepts the true premise and provides a detailed, relevant framework for preventing direct and indirect prohibited transactions. |
| CORRECT | A platform should use a **risk-based, layered sanctions-control program** that blocks both direct and indirect connections to the prohibited jurisdictions. Key controls include:
1. **Define the prohibited scope**
- Maintain an up-to-date list of prohibited countries and regions, including Cuba, Iran, North Korea, Syria, Crimea, Donetsk, and Luhansk.
- Include related territories, sanctioned persons and entities, and applicable ownership rules—such as entities owned 50% or more by blocked persons where relevant.
- Keep the list synchronized with Stripe’s requirements, OFAC and other applicable sanctions authorities, and legal counsel.
2. **Screen all relevant parties**
Screen at onboarding and periodically thereafter:
- Customers and account holders
- Businesses, beneficial owners, directors, and authorized users
- Sellers, suppliers, contractors, recipients, and payout beneficiaries
- Shipping, billing, and fulfillment parties
- Banks, payment instruments, and other intermediaries
Screening should use name aliases, transliterations, dates of birth, addresses, ownership data, and sanctions-list updates.
3. **Verify location and residency**
Do not rely only on a user-selected country. Use multiple signals, such as:
- Government identity and business-registration documents
- Residential and business addresses
- IP address and geolocation
- Device and network characteristics
- Phone number and tax information
- Bank-account country and card-issuer country
- Shipping and delivery addresses
Conflicting or high-risk signals should trigger a hold or manual review rather than automatic approval.
4. **Screen products, services, and transaction purpose**
- Require merchants to describe what they sell and where goods or services originate, are delivered, or are performed.
- Review listings, invoices, free-text descriptions, URLs, and shipping information for prohibited-country indicators and evasion terms.
- Prevent use of generic descriptions intended to conceal the actual goods, services, destination, or counterparty.
- Apply controls to digital goods, software, consulting, travel, logistics, and other services—not only physical shipments.
5. **Block transactions using hard controls**
Configure the platform to automatically decline or prevent:
- Transactions involving a prohibited location or sanctioned party
- Payouts to prohibited jurisdictions
- Cards or bank accounts issued or located there
- Shipping or service-performance addresses there
- Transactions where the platform cannot reasonably establish the parties’ or activity’s location
Do not allow users to bypass the control by changing billing details, using an intermediary, splitting payments, or routing funds through another country.
6. **Monitor for indirect dealings and evasion**
Use rules and analytics to detect:
- Rapid changes of address, IP, device, or payment method
- VPN, proxy, or anonymization use
- Unusual payment-routing patterns
- Common counterparties connected to prohibited jurisdictions
- Repeated failed attempts with slightly altered customer details
- Third parties acting as fronts or pass-through entities
- Mismatches between customer location, product origin, and delivery location
7. **Hold, investigate, and escalate**
Establish a documented workflow for:
- Temporary holds on suspicious transactions and payouts
- Enhanced due diligence and requests for supporting documents
- Compliance review of potential sanctions matches
- Rejection, account suspension, or termination
- Reporting or other action where legally required
- Prohibition on telling a customer that a suspicious-activity report was filed, where applicable
8. **Control onboarding and platform design**
- Put sanctions restrictions in merchant terms, customer terms, and acceptable-use policies.
- Make merchants responsible for accurate location, ownership, product, and fulfillment information.
- Use country restrictions in account creation, checkout, payouts, and API flows.
- Ensure customer support cannot manually override a sanctions block without authorized compliance approval.
- Apply the same controls to refunds, credits, chargebacks, transfers, and marketplace payouts.
9. **Maintain governance and evidence**
- Assign a compliance owner and clear escalation authority.
- Test screening and blocking rules regularly, including attempted evasion scenarios.
- Keep audit logs showing screening results, decisions, overrides, and supporting evidence.
- Train staff and update controls when Stripe, sanctions authorities, or applicable laws change.
- Review vendors that provide KYC, screening, geolocation, fraud, and payment services.
A practical minimum is: **verify identity and location, screen all parties and beneficial owners, inspect the transaction and fulfillment details, automatically block prohibited connections, and investigate ambiguous or indirect links before releasing funds.** The exact scope should be validated against Stripe’s current contractual requirements and the laws applicable to the platform and its users. The answer accepts the true premise and provides detailed, relevant controls for preventing direct and indirect prohibited-jurisdiction transactions. |
| CORRECT | A platform should implement a **sanctions and geographic-controls program that blocks both obvious and indirect exposure**, rather than relying only on Stripe’s automated checks.
### Recommended controls
1. **Screen users and businesses before onboarding**
- Collect and verify legal name, address, nationality/incorporation country, operating locations, beneficial owners, directors, and authorized representatives.
- Screen all relevant parties against applicable sanctions lists, including OFAC and other lists required by the platform’s jurisdictions.
- Reject or suspend accounts located in, organized in, owned or controlled from, or operating in Cuba, Iran, North Korea, Syria, or the Crimea, Donetsk, and Luhansk regions.
- Re-screen users periodically and whenever their ownership, address, or risk profile changes.
2. **Determine the real location of the transaction**
Check more than the customer’s billing address. Consider:
- IP address and device/location signals;
- shipping, delivery, pickup, and service-performance locations;
- card, bank-account, and wallet country;
- merchant and customer addresses;
- place of incorporation and beneficial ownership;
- VPN, proxy, anonymizer, or inconsistent-location indicators.
These signals should be used together. IP geolocation alone is not sufficient.
3. **Screen the goods, services, and counterparties**
Since the prohibition covers goods or services linked **directly or indirectly** to the restricted jurisdictions, review:
- product and service descriptions, URLs, invoices, and merchant category;
- destination, origin, and transit locations;
- suppliers, distributors, agents, contractors, and marketplaces;
- beneficiaries of payouts and refunds;
- digital goods or services delivered remotely;
- ownership or control links to restricted-region entities.
Do not permit a merchant to avoid the restriction merely by routing the transaction through an intermediary or by describing the product vaguely.
4. **Apply pre-transaction controls**
Before authorization or release of funds:
- screen the merchant, customer, payee, and other relevant parties;
- validate transaction geography and delivery/performance location;
- block prohibited matches and restricted-country exposure;
- place uncertain matches or suspicious routing in a manual-review queue;
- prevent capture, payout, transfer, refund, or withdrawal while a review is pending.
A blocked transaction should not be completed through another connected account, payment method, currency, or payout route.
5. **Use clear outcomes**
- **Hard block:** confirmed restricted jurisdiction, sanctioned party, prohibited product/service, or an attempt to circumvent controls.
- **Hold and investigate:** possible sanctions-list match, conflicting location data, unexplained intermediary, or high-risk transaction pattern.
- **Release:** only after documented review resolves the concern.
Avoid “approve by default” when required information is missing.
6. **Monitor after onboarding**
Continuously monitor for:
- sudden changes in IP, address, bank account, or ownership;
- repeated use of VPNs or proxy services;
- unusual third-party payments or payouts;
- shipping or service locations inconsistent with the account;
- rapid movement of funds through multiple accounts;
- attempts to split transactions or use alternate accounts after a decline;
- descriptions that change to conceal the actual product or destination.
7. **Maintain governance and evidence**
The platform should maintain:
- a written sanctions policy and restricted-country list;
- documented risk assessments and decision rules;
- audit logs showing screening results, alerts, decisions, and reviewer identity;
- procedures for escalation, account closure, blocked-funds handling, and regulatory reporting where applicable;
- regular updates to sanctions lists, geolocation data, rules, and screening vendors;
- employee and merchant training.
Stripe’s Treasury requirements and Restricted Businesses policy should be treated as a **minimum contractual requirement**, not as a substitute for the platform’s own controls. Stripe specifically identifies Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions as high-risk or restricted areas in its Treasury requirements. The platform should also obtain legal advice on applicable OFAC, local, and other sanctions regimes because the exact blocking, reporting, and licensing obligations can vary by jurisdiction. The answer accepts the true premise and provides detailed, relevant controls for preventing direct and indirect prohibited transactions. Stripe Treasury prohibited businesses Cuba Iran North Korea Syria Crimea Donetsk Luhansk sanctions5 results
results as cached 2026-08-24T07:05 OFAC sanctions compliance framework screening transaction geolocation red flags5 results
results as cached 2026-08-24T07:05 Stripe restricted businesses sanctions screening prohibited countries policy5 results
results as cached 2026-08-24T07:05 |
| CORRECT | A platform should treat this as a **sanctions-control requirement**, not merely a country filter. Stripe’s Treasury requirements prohibit dealings, engagement, or sales of goods or services linked **directly or indirectly** to Cuba, Iran, North Korea, Syria, and Crimea, Donetsk, and Luhansk. Controls should cover the platform, connected accounts, customers, recipients, counterparties, and transaction flows. [Stripe Treasury requirements](https://docs.stripe.com/treasury/connect/requirements)
### Recommended control framework
1. **Screen businesses before onboarding**
- Conduct KYB/KYC on the platform, connected accounts, beneficial owners, directors, authorized users, customers, and recipients.
- Screen names and identifying information against applicable sanctions lists, including OFAC lists and other lists relevant to the platform’s jurisdictions.
- Identify country of incorporation, principal place of business, operating locations, tax residence, bank accounts, and beneficial-owner residency.
- Reject or suspend applicants with a prohibited address, sanctioned-party match, or material nexus to a prohibited jurisdiction.
2. **Collect information about the underlying business**
- Require a clear description of the business, products, services, customers, suppliers, and expected countries of operation.
- Obtain contractual representations that the account will not be used for prohibited jurisdictions or sanctioned parties.
- Apply enhanced due diligence to marketplaces, import/export businesses, freight companies, high-risk industries, and businesses with complex ownership or international flows.
3. **Screen each transaction**
Screen relevant transaction data before funds are released, including:
- Sender, recipient, payer, payee, and intermediary names;
- Beneficial owners and counterparties;
- Billing, shipping, delivery, and operating addresses;
- Bank country and payment-instrument country;
- IP address, device, phone, and geolocation signals;
- Product or service descriptions, invoices, merchant category, and shipping routes.
Block transactions where the destination, origin, beneficiary, counterparty, or underlying goods or services are connected to a prohibited jurisdiction. Do not rely on IP geolocation alone, since it can be evaded or may not identify the true business nexus.
4. **Prevent indirect circumvention**
Use rules and investigations to identify attempts to route transactions through third countries, shell companies, nominees, resellers, freight forwarders, or payment intermediaries. Red flags include:
- A customer’s location conflicting with its stated address;
- Recently changed ownership or banking details;
- Payments involving high-risk intermediary jurisdictions;
- Shipping routes inconsistent with the transaction;
- Vague invoices or mismatches between the stated business and transaction activity;
- Common ownership, control, devices, addresses, or bank accounts linking multiple accounts.
5. **Use a decisioning workflow**
- **Auto-decline or block** confirmed matches and prohibited-country indicators.
- **Place transactions and accounts on hold** for potential matches or unclear indirect links.
- Route alerts to trained sanctions/compliance personnel for investigation.
- Do not release funds until the alert is cleared.
- Escalate reportable activity and suspected violations as required by applicable law and Stripe’s instructions. Avoid notifying a person that a sanctions investigation or report has been made where prohibited.
6. **Monitor after onboarding**
- Rescreen customers, connected accounts, owners, and counterparties periodically and whenever sanctions lists change.
- Monitor transaction behavior and geographic anomalies.
- Reverify accounts after changes to ownership, address, bank account, products, or countries served.
- Have a documented process to suspend, terminate, and investigate accounts that later develop a prohibited nexus.
7. **Maintain governance and evidence**
- Keep written policies, risk ratings, screening results, alert dispositions, approvals, blocked transactions, and customer communications.
- Maintain current sanctions lists and test screening logic for name variations, transliteration, aliases, and false positives.
- Train relevant personnel and periodically test the controls.
- Make the controls consistent with Stripe’s current requirements and obtain Stripe approval where required; do not assume that a transaction is permissible merely because it is technically supported by the API.
In practice, the platform should implement a **layered control**: onboarding screening + beneficial-owner and business due diligence + transaction screening + geolocation and payment controls + ongoing monitoring + manual escalation. The specific rules should be reviewed by sanctions counsel and coordinated with Stripe, because the prohibition covers indirect links and Stripe’s requirements may be broader than a particular sanctions list. The answer accepts the true premise and provides a detailed, relevant sanctions-control framework for preventing direct and indirect prohibited transactions. site:stripe.com restricted businesses sanctions screening Stripe prohibited countries5 results
results as cached 2026-08-24T07:05 site:stripe.com Treasury prohibited businesses Cuba Iran North Korea Syria Crimea Donetsk Luhansk4 results
results as cached 2026-08-24T07:05 OFAC sanctions compliance framework screening geolocation customer due diligence transaction monitoring official5 results
results as cached 2026-08-24T07:05 opened 1 page
|
| CORRECT | A platform should implement a **preventive sanctions-compliance program** with controls at onboarding, account use, and transaction execution—not merely screen the payer’s name.
### 1. Screen all relevant parties
Before enabling Treasury or payment functionality, screen:
- Customers, merchants, suppliers, and recipients
- Beneficial owners, directors, and authorized representatives
- Banks, payment intermediaries, and counterparties
- Shipping, billing, and fulfillment parties where relevant
Screen against applicable sanctions lists, including OFAC and other required lists, and specifically identify ties to:
- Cuba
- Iran
- North Korea
- Syria
- Crimea, Donetsk, and Luhansk
Use fuzzy-name matching, transliteration, aliases, ownership analysis, and periodic rescreening.
### 2. Verify geographic information
Collect and validate:
- Country of residence and incorporation
- Registered and operating addresses
- IP address and device location
- Phone-country code
- Bank and card issuing country
- Shipping and billing addresses
- Beneficiary and sender locations
- Destination of goods or services
Do not rely on a single country field. Investigate inconsistencies, VPN or proxy use, unusual routing, and attempts to conceal a restricted location.
### 3. Understand the business and transaction
At onboarding and periodically thereafter, determine:
- What goods or services the user sells
- Where they are produced, delivered, or consumed
- Who the ultimate customer and beneficiary are
- Whether agents, distributors, resellers, or marketplaces are involved
- Whether the transaction is connected indirectly to a prohibited jurisdiction
Use product descriptions, URLs, invoices, order data, merchant category codes, customs/shipping information, and marketplace metadata. Prohibit restricted countries and territories in supported-country, shipping, billing, and beneficiary fields.
### 4. Enforce blocking controls
Configure hard blocks—not user-facing warnings—for transactions involving a prohibited connection. Controls should apply to:
- Account creation and verification
- Account funding and withdrawals
- Payouts and transfers
- Card issuance and use
- Payment authorization and capture
- Refunds and credits
- Marketplace split payments
- Subscription renewals
- Cross-border settlement
If a transaction is blocked, do not reroute, retry, split, relabel, or use another payment method to complete it.
### 5. Monitor for indirect circumvention
Use rules and risk scoring for indicators such as:
- Payments routed through unrelated third countries
- Repeated changes to address, beneficiary, or bank information
- Third-party funding or payouts
- Shell companies or nominee owners
- Mismatched IP, device, billing, and shipping data
- Unusual corridors, currencies, or transaction volumes
- Descriptions that obscure the actual goods or services
- Customers using intermediaries to reach a restricted jurisdiction
High-risk cases should be held pending review; confirmed matches should be rejected, restricted, or offboarded according to the platform’s procedures and Stripe’s requirements.
### 6. Establish escalation and reporting procedures
Maintain a documented workflow for:
- Automatic holds
- Manual sanctions review
- False-positive resolution
- Account freezes or suspension
- Return or rejection of funds where legally and contractually permitted
- Notification to Stripe
- Regulatory reporting, where required
- Preservation of evidence and audit logs
Do not disclose unnecessary details about screening logic to a suspected evader.
### 7. Apply contractual and technical safeguards
User agreements should prohibit:
- Use of the platform for dealings involving restricted jurisdictions
- Indirect facilitation through agents or intermediaries
- Circumvention of geographic or sanctions controls
- False or misleading onboarding information
Require users to provide accurate information, permit verification, and cooperate with investigations. Restrict API fields and workflows so users cannot bypass country, beneficiary, or product controls.
### 8. Test and document the program
The platform should maintain:
- Written sanctions policies and risk assessments
- A clear ownership model for compliance decisions
- Audit trails for screening and blocking decisions
- Periodic list updates and rescreening
- Rule and model testing
- Staff training
- Independent reviews or audits
- Incident-response and remediation procedures
Because Stripe Treasury may impose requirements stricter than general legal minimums, the platform should treat Stripe’s contractual restrictions as a **hard product constraint** and obtain compliance or legal advice before relying on any sanctions-license exception. The answer accepts the true premise and provides detailed, relevant controls for preventing directly or indirectly prohibited transactions. |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
1 Stripe Treasury for platforms has compliance requirements and restrictions that apply to the platform and its connected accounts, customers, and recipients. Offer your Stripe Treasury-based financial services only to businesses that meet the requirements.
2 ## Availability
3 * Treasury for platforms is in public preview for platforms and connected accounts in the UK.
| CORRECT | A platform can offer Stripe Treasury–based financial services to its **eligible connected business accounts**—not directly to arbitrary consumers.
Typically, the business must:
- Be onboarded to the platform through **Stripe Connect**
- Be located in a country supported by the relevant Stripe Treasury product—currently primarily the **US and UK**, with availability depending on the product and platform setup
- Be a legitimate business, rather than an individual consumer
- Pass Stripe’s **KYC, sanctions, risk, and underwriting checks**
- Operate in an industry permitted by Stripe and its financial partners
- Meet any requirements for the specific service, such as receiving payments, holding funds, issuing cards, or making payouts
Availability, account types, and permitted use cases vary by country and product, so Stripe must approve both the platform and the connected businesses. It states that services may be offered only to eligible businesses that meet Stripe Treasury and related platform requirements, consistent with the source. |
| CORRECT | A platform can offer Stripe Treasury financial services to **eligible business users connected to its platform**, typically:
- **Businesses located in the same supported country as the platform/Treasury program**—currently the **US or UK**, depending on the program.
- **Business entities such as corporations, LLCs, partnerships, and eligible sole proprietorships**.
- Connected accounts that pass **Stripe’s KYC, sanctions, risk, and prohibited-business checks**.
Stripe Treasury is intended for **businesses, not consumers or personal accounts**. Availability also depends on the platform’s approval, the connected account’s country and business structure, and the specific Treasury products being offered. It states that services may be offered only to eligible businesses that meet Stripe Treasury requirements, which matches the source. |
| CORRECT | A platform can offer Stripe Treasury services to its **Stripe Connect connected accounts**—typically **businesses and sole proprietorships**, rather than individual consumers—provided they:
- Are located in a country where Stripe Treasury is supported
- Meet Stripe’s business, KYC/KYB, sanctions, and risk requirements
- Have the required Connect capabilities and account status
- Operate in an industry permitted by Stripe and its banking partners
The exact availability depends on the platform’s and connected account’s country, business structure, and use case. Treasury isn’t generally available for arbitrary third parties or personal accounts; eligibility must be approved by Stripe. It states that Treasury services may be offered only to businesses meeting Stripe's applicable requirements, consistent with the source. |
| CORRECT | A platform can offer Stripe Treasury-based financial services to **eligible business customers connected through Stripe Connect**, provided the use case is **B2B—not consumer banking**.
Generally, the connected business must:
- Be located in a Stripe-supported region.
- Have a valid physical business address (not a PO box, private mailbox, or registered-agent address; U.S. Treasury accounts require a U.S.-based physical business).
- Have a representative based in the same country as the business.
- Provide a publicly accessible website or a sufficiently detailed description of its products or services.
- Pass Stripe’s identity, compliance, fraud, and risk reviews.
- Be onboarded by the platform rather than using a Stripe-hosted dashboard.
Examples of potentially eligible businesses include companies using a platform to **hold funds, manage cash flow, pay vendors or contractors, receive transfers, or issue commercial cards**.
Stripe does **not** publish a simple exhaustive whitelist. Businesses are prohibited or restricted based on their industry and activities. Prohibited examples include:
- Adult, escort, or dating services
- Arms trading
- ATMs
- Casinos, gambling, or gaming
- Debt collection or credit restoration
- Government entities
- Marijuana or illegal-drug businesses
- Money services and currency exchange
- Peer-to-peer payment businesses
- Payday lending
- Shell corporations
- Pyramid or deceptive marketing schemes
Restricted businesses—such as marketplaces, lenders, insurance and investment firms, pharmaceuticals, tobacco, BNPL providers, lawyers/accountants, NGOs, NFT businesses, and virtual-asset service providers—may require enhanced review or explicit Stripe approval.
Eligibility ultimately depends on Stripe and its financial-services partners’ review. It states that services may be offered only to eligible businesses that meet Stripe Treasury requirements, which matches the source. site:docs.stripe.com treasury businesses can offer financial services platforms connected accounts eligibility United States businesses5 results
results as cached 2026-08-24T07:03 opened 2 pages |
| CORRECT | A platform can offer **Stripe Treasury-based financial services only to eligible business customers in B2B use cases**—not to consumers or for consumer purposes.
Eligible businesses must generally:
- Be located in a supported region and have a valid physical business address.
- Pass Stripe’s connected-account onboarding, KYC/KYB, and compliance reviews.
- Use Treasury for legitimate business activities.
- Not be connected to jurisdictions Stripe considers high risk.
- Meet Stripe’s fraud-prevention and account-security requirements.
**Prohibited businesses** cannot use Treasury for platforms, including businesses involved in:
- Adult, escort, or dating services
- Arms trading
- ATMs
- Bail bonds
- Casinos, gambling, or gaming
- Debt collection, debt relief, or credit restoration
- Government entities
- Direct hemp or marijuana businesses
- Illegal drugs
- Money services or currency exchange
- Peer-to-peer payments
- Shell corporations
- Payday lending
- Telecommunication or surveillance equipment
- Pyramid schemes or deceptive practices
- Unregistered charities
- Warranties or lifetime guarantees
**Restricted businesses**—such as lenders, insurance or investment firms, marketplaces, pharmaceuticals, tobacco companies, BNPL providers, NGOs, NFT businesses, professional service providers, pawnshops, payment processors, and virtual-asset businesses—may be eligible only after enhanced review and, in some cases, explicit Stripe approval.
See Stripe’s [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements). It states that services may be offered only to eligible businesses that meet Stripe Treasury requirements, which matches the source. site:docs.stripe.com/treasury businesses can offer financial services Stripe Treasury-based financial services platform eligible businesses5 results
results as cached 2026-08-24T07:03 opened 1 page
|
| CORRECT | A platform can offer **Stripe Treasury-based financial services only to eligible businesses in a B2B use case**—not to consumers or for consumer purposes.
Connected businesses must generally:
- Be located in a supported region and have a valid physical business address
- Pass Stripe’s eligibility, identity, compliance, and fraud reviews
- Not be linked to prohibited jurisdictions or illegal activity
- Use Treasury for business purposes
**Prohibited businesses include**, among others:
- Adult, escort, or dating services
- Arms dealers and ATMs
- Bail bonds
- Casinos, gambling, or gaming
- Debt collection or debt-relief businesses
- Government entities
- Marijuana or illegal-drug businesses
- Money services and currency-exchange businesses
- Payday lenders
- Peer-to-peer payment businesses
- Shell corporations
- Unregistered charities
- Multi-level marketing or deceptive practices
**Restricted businesses**—such as insurers, lenders, brokerages, marketplaces, pharmaceuticals, tobacco companies, NGOs, NFT businesses, professional service providers, and virtual-asset businesses—may be eligible only after enhanced review or explicit Stripe approval.
Stripe’s requirements are subject to change and regional availability; see the [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements). It states that services may be offered only to eligible businesses that meet Stripe Treasury requirements, matching the source. site:docs.stripe.com/treasury businesses can offer financial services Stripe Treasury platforms eligible businesses5 results
results as cached 2026-08-24T07:03 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
6 For all supported regions, [contact sales](https://stripe.com/contact/embedded-finance) to request access to Treasury for platforms.
7 Your business must physically operate from, and have at least one account representative who lives at, an address within a supported region. These addresses can’t be a PO box, highway contract box, or private mailbox. Business owners who reside outside a supported region might require enhanced review.
8 Stripe prohibits using Treasury for any dealings, engagement, or sale of goods or services linked directly or indirectly with jurisdictions Stripe deems high risk, such as Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions.
9 Your connected accounts must be [eligible](https://docs.stripe.com/treasury/connect/account-management/connected-accounts#eligibility).
10 ## Fraud management process
| CORRECT | Stripe Treasury generally prohibits dealings involving comprehensively sanctioned jurisdictions:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea, including Sevastopol**
- **The Donetsk and Luhansk regions of Ukraine**
Transactions involving sanctioned persons or entities are also prohibited, even if they are located elsewhere. **Russia, Belarus, and other higher-risk jurisdictions may be subject to additional restrictions or review rather than being universally prohibited.** Stripe’s current Treasury terms and sanctions-screening results control, so the list should be checked against Stripe’s latest policy before onboarding or processing a transaction. It lists Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions, matching the source. |
| CORRECT | Stripe Treasury generally prohibits dealings involving jurisdictions subject to comprehensive U.S. sanctions, including:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea, Sevastopol, Donetsk, and Luhansk regions of Ukraine**
Stripe may also restrict transactions involving other sanctioned countries, territories, governments, or persons—including certain dealings connected with **Russia, Belarus, Venezuela, Sudan, and Myanmar**—depending on the activity and applicable sanctions. The exact list can change, so Stripe’s current sanctions and prohibited-businesses policy should be checked before relying on it. It includes all jurisdictions named in the source: Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions. |
| CORRECT | Stripe Treasury generally prohibits dealings involving jurisdictions subject to comprehensive U.S. sanctions:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea, Donetsk, and Luhansk regions of Ukraine**—including other Ukrainian territories subject to applicable sanctions
The list can change as sanctions regimes are updated, and Stripe may also prohibit specific transactions involving other sanctioned or high-risk locations. Check Stripe’s current Treasury terms and sanctions guidance for the controlling list. The answer lists Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions, matching the source. |
| CORRECT | Stripe prohibits Stripe Treasury dealings—directly or indirectly—with these high-risk jurisdictions:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea**
- **Donetsk region**
- **Luhansk region**
This includes persons located in, resident in, or citizens of those jurisdictions, as well as products or services originating there. Stripe describes the list as including jurisdictions such as these, so additional restrictions may apply based on sanctions, financial partners, or applicable law. [Stripe Treasury requirements](https://docs.stripe.com/treasury/connect/requirements) It lists Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions, matching the source. site:stripe.com Treasury high-risk jurisdictions prohibited Stripe Treasury dealings5 results
results as cached 2026-08-24T07:03 Stripe Treasury prohibited jurisdictions high risk countries5 results
results as cached 2026-08-24T07:03 Stripe Treasury terms restricted businesses jurisdictions sanctions5 results
results as cached 2026-08-24T07:03 opened 3 pages
|
| CORRECT | Stripe prohibits Treasury dealings—directly or indirectly—linked to these high-risk jurisdictions:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea**
- **Donetsk region**
- **Luhansk region**
This includes dealings with persons located in, resident in, or citizens of those jurisdictions, as well as products or services originating there. Stripe’s list may change and can include other sanctioned persons or entities, so consult the applicable Stripe Services Agreement and sanctions requirements for your region. The answer lists Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions, matching the source. site:stripe.com Treasury prohibited high-risk jurisdictions Stripe Treasury5 results
results as cached 2026-08-24T07:03 Stripe Treasury high risk jurisdictions prohibited countries5 results
results as cached 2026-08-24T07:03 Stripe Treasury prohibited jurisdictions sanctions high risk5 results
results as cached 2026-08-24T07:03 opened 3 pages |
| CORRECT | Stripe lists these **high-risk jurisdictions as prohibited** for direct or indirect dealings, engagements, or sales of goods or services:
- **Cuba**
- **Iran**
- **North Korea**
- **Syria**
- **Crimea region**
- **Donetsk region**
- **Luhansk region**
Stripe also prohibits dealings with persons or entities on applicable U.S., U.K., E.U., or U.N. restricted-party lists. Additional Russia-related restrictions apply to certain services and goods.
Source: [Stripe Prohibited and Restricted Businesses](https://stripe.com/legal/restricted-businesses) The answer lists Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions, matching the source. site:stripe.com Treasury prohibited high-risk jurisdictions Stripe Treasury dealings5 results
results as cached 2026-08-24T07:03 opened 1 page |
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
15 * Conducting root cause analyses after fraud incidents occur to identify opportunities to improve controls.
16 ## Business use cases only
17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
18 ## Prohibited and restricted business types
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
| CORRECT | Financial accounts through **Stripe Treasury for platforms** are generally available to eligible **connected business accounts** on Connect platforms—not to ordinary consumers.
Eligibility typically requires that the connected account:
- Is in a country and business type supported by Treasury
- Completes Stripe’s identity, business, and KYC verification
- Meets Stripe’s risk and compliance requirements
- Has the **Treasury capability** enabled by the platform
Eligible businesses may include companies, nonprofits, and—in supported cases—sole proprietorships. Availability, account features, and geographic requirements vary by country, and Stripe makes the final eligibility determination. It states that financial accounts are for connected business accounts on platforms and not consumers, consistent with the source's B2B-only restriction. |
| CORRECT | Stripe Treasury financial accounts are available to **eligible connected business accounts on participating platforms**. In general:
- The connected account must be a **business**, not an individual or consumer account.
- It must be located in a **supported country or region**—currently availability depends on the specific Stripe Treasury program and country.
- The business and platform must pass Stripe’s **KYC, sanctions, and risk reviews**.
- The platform must be approved for **Financial Accounts for platforms** and request the appropriate Treasury capabilities for the connected account.
Eligibility isn’t automatic: Stripe determines whether a platform and each connected account qualify. Availability and requirements can vary by country and business type, so the platform should check the current Stripe Treasury documentation or contact Stripe. It states that financial accounts are for business use rather than consumers, consistent with the source's B2B-only eligibility. |
| CORRECT | Stripe Treasury financial accounts are available to **eligible connected accounts on approved Stripe platforms**—not to arbitrary consumers directly.
Generally, the connected account must:
- Be a business or organization in a country supported by Stripe Treasury
- Have the required business, owner, and representative information verified through Connect/KYC
- Operate in an industry and use case permitted by Stripe and its banking partners
- Meet Stripe’s risk, compliance, and eligibility requirements
Availability varies by country and account type, and Stripe may restrict certain businesses or individuals. The platform must also be approved for Treasury and request the appropriate `treasury` capability for the connected account. It states that financial accounts are for eligible business or organization connected accounts on approved platforms and not consumers, consistent with the source's B2B-only restriction. |
| CORRECT | Stripe Treasury for platforms is available to **business-focused Connect platforms and eligible connected business accounts**, subject to Stripe approval and regional availability.
Generally:
- The platform must have a **B2B use case**—Treasury financial accounts aren’t offered for consumer purposes.
- The platform must operate in a supported region and have an account representative residing there.
- Connected accounts must be based in a supported region, have a valid publicly accessible website or a sufficiently detailed product description, and have an account representative in the same country.
- The platform must collect required business, identity, ownership, and compliance information.
- Connected accounts must not be prohibited or restricted businesses, and businesses owned by politically exposed persons aren’t eligible.
- The connected account must use a platform-controlled integration rather than a Stripe-hosted dashboard, with the platform responsible for requirements collection.
- Stripe must review and activate the requested `money_manager` capabilities.
Availability currently varies by region: public preview in the UK and private preview in the US and EU, with access requested through Stripe sales. It states that Treasury for platforms is for B2B use cases and not available for consumer purposes, matching the source. site:docs.stripe.com treasury financial accounts platforms who can get financial accounts eligibility5 results
results as cached 2026-08-24T07:03 opened 2 pages
|
| CORRECT | Stripe Treasury for platforms is generally available to:
- **US-based platforms** using Stripe Connect.
- **US-based business users/connected accounts** onboarded to the platform.
- Businesses that pass Stripe’s **KYC, sanctions, risk, and eligibility reviews**.
- Businesses that aren’t in Stripe’s **restricted or prohibited industries**.
Eligibility is determined **account by account**, so a platform or connected account may be approved while another is not. Individuals and restricted business types may be ineligible. Stripe must also approve the platform before it can provision financial accounts for eligible connected accounts.
See Stripe’s [Treasury for platforms eligibility guidance](https://support.stripe.com/questions/how-do-i-know-if-my-account-is-eligible-for-treasury-for-platforms). It identifies business/connected-account use rather than consumer use, which is consistent with Treasury for platforms being limited to B2B use cases and unavailable for consumer purposes. site:stripe.com/docs/treasury financial accounts for platforms who can get financial accounts0 results
results as cached 2026-08-24T07:04 Stripe Treasury financial accounts for platforms eligibility who can get accounts5 results
results as cached 2026-08-24T07:04 opened 3 pages
|
| CORRECT | Stripe Treasury for platforms is available to:
- **Connect platforms with a business-to-business (B2B) use case**—not consumer-facing financial accounts.
- **Eligible connected accounts** in supported regions. They must generally:
- Be based in a supported region.
- Have a valid, publicly accessible website or a detailed product/service description.
- Have an account representative located in the same country as the business.
- Provide required business, owner, identity, and compliance information.
- Have a valid physical business address—not a PO box, private mailbox, or registered-agent address. Stripe’s current requirements specifically state that connected accounts must have a US-based physical business address.
- **Businesses such as sole proprietorships, LLCs, corporations, and nonprofits**, subject to Stripe’s review and approval.
The platform itself must operate physically in a supported region, have a representative living there, manage onboarding and compliance requirements, and obtain access from Stripe. Certain prohibited businesses—such as gambling, money services, P2P payments, illegal products, and shell companies—aren’t eligible; restricted industries require enhanced review. It states that Treasury for platforms is for B2B platforms and not for consumer-facing financial accounts, matching the source. site:docs.stripe.com treasury financial accounts for platforms who can get financial accounts requirements5 results
results as cached 2026-08-24T07:04 opened 2 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
18 ## Prohibited and restricted business types
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
20 #### Warning
21 Businesses that offer illegal products or services are never eligible to use Treasury for platforms.
| CORRECT | A business in a **restricted category** may use Stripe Treasury for platforms only if:
- **Stripe gives prior written approval** after reviewing the business and its proposed use.
- The business is **not a prohibited business** under Stripe’s rules.
- Treasury is used only for the **approved activities, products, geographies, and account types**.
- The platform and its connected accounts satisfy Stripe’s **KYC/KYB, AML, sanctions, financial-partner, and other compliance requirements**.
- The business complies with any **additional conditions or controls** Stripe imposes.
Approval is discretionary and may be limited or withdrawn. A platform should not onboard restricted businesses or use Treasury to support restricted activities unless Stripe has expressly approved that arrangement. It states that a restricted business may use Treasury for platforms with Stripe's explicit prior approval, which matches the source. |
| CORRECT | A business in a **restricted industry** may use Stripe Treasury for platforms only on a **case-by-case basis**, subject to Stripe’s prior approval. Typically:
- The business must not be **prohibited** from using Stripe or Treasury.
- Stripe must complete and approve any required **underwriting, KYC/KYB, and compliance review**.
- The platform and connected accounts must satisfy Treasury’s **country, entity, ownership, and product eligibility requirements**.
- The platform must implement required **AML, sanctions, fraud, transaction-monitoring, and user-verification controls**.
- Stripe may impose additional conditions, such as **reserves, transaction or balance limits, enhanced reporting, or restrictions on the funds’ use**.
- The business may use Treasury only for the **approved activities**; approval for Stripe Payments does not automatically authorize Treasury access.
Businesses classified as **prohibited**, rather than merely restricted, generally cannot use Stripe Treasury. Availability and requirements also vary by jurisdiction and can change, so the business must obtain confirmation from Stripe before launching. It correctly states that a restricted business may use Treasury for platforms in some cases after obtaining prior explicit approval from Stripe. |
| CORRECT | A restricted business may use **Stripe Treasury for platforms only with Stripe’s prior approval** and on a case-by-case basis. Typically, Stripe must determine that:
- The business and its connected accounts meet Treasury and Connect eligibility requirements.
- The proposed use complies with applicable banking, payments, AML/KYC, sanctions, and money-transmission laws.
- The business is not engaging in a **prohibited** activity.
- The platform can satisfy any enhanced due-diligence, monitoring, reserve, reporting, or other conditions Stripe imposes.
Approval is discretionary and may be limited or withdrawn. Businesses should disclose their business model and intended Treasury flow to Stripe before integrating; being classified as “restricted” does not by itself mean approval is available. It correctly states that a restricted business may use Treasury for platforms in some cases only after explicit approval from Stripe. |
| CORRECT | A restricted business may use **Stripe Treasury for platforms only if Stripe explicitly approves it** after an enhanced compliance review. Approval is discretionary and may depend on Stripe’s financial-services partners, applicable laws, and network rules.
The business must also generally:
- Operate from a supported region and meet Stripe’s platform and connected-account eligibility requirements.
- Use Treasury only for **B2B purposes**—not consumer financial accounts or consumer use cases.
- Maintain processes to identify customers, prevent unauthorized access and fraud, and respond to fraud incidents.
- Avoid dealings connected to jurisdictions Stripe considers high risk.
- Comply with any additional conditions Stripe imposes for the particular industry.
Businesses involved in **illegal products or services are never eligible**, and prohibited categories cannot use Treasury even with approval. Thus, being “restricted” means possible case-by-case approval; it does not guarantee access. It correctly states that a restricted business may use Stripe Treasury for platforms in some cases after explicit approval from Stripe. site:stripe.com Treasury for platforms restricted businesses circumstances use Stripe Treasury for platforms5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | A **restricted business** may use Stripe Treasury for platforms only if:
- It passes Stripe’s **enhanced compliance and risk review**.
- Stripe gives it **explicit approval**, where required.
- The relevant **financial-services provider and network rules** also permit the activity.
- The business complies with Stripe’s other Treasury requirements, including:
- A legitimate **B2B use case**—Treasury isn’t offered for consumer purposes.
- Operating in a supported region and meeting applicable account/address requirements.
- Not being connected directly or indirectly to jurisdictions Stripe considers high risk.
- Maintaining appropriate fraud-prevention, monitoring, and remediation processes.
- Ensuring connected accounts are themselves eligible.
Approval is discretionary and depends on the specific business model, products, geography, licensing, ownership, and the particular Treasury service. A business offering **illegal products or services is never eligible**, and businesses in prohibited categories cannot use Treasury even with approval. Examples of restricted categories that may be reviewed include insurance, lending, marketplaces, BNPL, pharmaceuticals, tobacco, NFTs, NGOs, professional service providers, and virtual-asset businesses. It states that a restricted business may use Treasury for platforms in some cases with explicit Stripe approval, which matches the source. site:stripe.com Treasury for platforms restricted businesses circumstances5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | A restricted business may use Stripe Treasury for Platforms **only after enhanced review and explicit approval from Stripe**. Approval is not automatic and may depend on:
- The specific business model and use case
- Financial-network rules and the requirements of Stripe’s financial-services providers
- Stripe’s legal and compliance obligations
- Whether the platform and its connected accounts meet Treasury eligibility requirements
- The business maintaining appropriate fraud-risk and compliance controls
Stripe’s restricted categories include, among others, insurance, investment and brokerage services, lending, MSBs, pharmaceuticals, tobacco, BNPL, marketplaces, NGOs, NFTs, professional service providers, payment processors, supplements, and virtual-asset service providers.
Businesses involved in **illegal products or services are never eligible**, and businesses in Stripe’s prohibited categories cannot use Treasury for Platforms. Treasury is also limited to **B2B use cases**, not consumer financial accounts or consumer purposes.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It states that a restricted business may use Treasury for platforms in some cases after explicit approval from Stripe, matching the source. site:docs.stripe.com treasury restricted businesses platforms circumstances can use Stripe Treasury for platforms5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
17 Treasury for platforms is available only to platforms with B2B use cases. Stripe doesn’t offer financial accounts to consumers or provide Treasury for platforms features for consumer purposes.
18 ## Prohibited and restricted business types
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
20 #### Warning
21 Businesses that offer illegal products or services are never eligible to use Treasury for platforms.
| CORRECT | Stripe’s **Treasury restricted-businesses list** covers businesses and activities that Stripe or its banking partners generally cannot support—or may support only after additional review—through Treasury financial accounts and related products.
Broadly, it includes:
- **Illegal goods or services**
- **Adult content or services**
- **Gambling, betting, and gaming**
- **Weapons, ammunition, and related products**
- **Drugs, controlled substances, marijuana, and drug paraphernalia**
- **Financial products and services**, such as money transmission, lending, securities, investment services, and other regulated financial activity
- **Cryptocurrency and virtual-asset businesses** in certain circumstances
- **Regulated or high-risk products**, including some pharmaceuticals, medical products, and pseudo-pharmaceuticals
- **Businesses handling or holding funds for third parties**, where the activity resembles escrow, money movement, or custodial financial services
- Other activities restricted by applicable **law, banking-partner rules, sanctions, or country-specific requirements**
The list is broader than simply “illegal businesses”: a legitimate business can still be ineligible for Treasury because of its industry, transaction flow, use of funds, or regulatory requirements. “Restricted” may mean either prohibited or subject to Stripe’s review and approval.
Stripe’s policy changes and varies by jurisdiction, so the current Treasury section of Stripe’s **Prohibited and Restricted Businesses** page is the authoritative source. The answer describes the restricted-businesses list as covering various restricted or prohibited categories while indicating it is broader than the examples given and may require review or approval, consistent with the source’s representative, non-exhaustive framing. |
| INCOMPLETE | Stripe’s **restricted businesses list for Treasury** covers business activities that Stripe generally:
- **Prohibits outright**, or
- **Allows only after review, with specific licenses, controls, or approval**
It typically includes categories such as:
- **Illegal or highly regulated goods and services**, including controlled substances, cannabis-related activity, pharmaceuticals, weapons, explosives, and counterfeit goods
- **Adult and sexual-content businesses**
- **Gambling, betting, lotteries, and gaming with monetary prizes**
- **Financial and money-movement businesses**, such as money transmitters, remittance providers, currency exchanges, check-cashing services, debt collection, lending, securities/investment services, and insurance
- **Cryptocurrency, virtual-currency, and related activities**, depending on the product and jurisdiction
- **Multi-level marketing, pyramid schemes, get-rich-quick programs, and deceptive business models**
- **Businesses connected with sanctions, evasion, fraud, or other unlawful conduct**
- Certain **high-risk marketplaces, crowdfunding, donations, or stored-value/payment activities**
“Restricted” does not always mean automatically banned. Stripe may assess the company’s business model, licenses, geography, owners, customers, transaction flows, and use of Treasury. Restrictions can also differ by country and by Treasury product, such as financial accounts, cards, or money movement.
The controlling source is Stripe’s current **Prohibited and Restricted Businesses** documentation and the terms applicable to your specific Treasury account. It describes restricted and prohibited business types but does not state the source’s key point that the listed categories are representative rather than exhaustive. |
| CORRECT | Stripe’s **Treasury restricted-business list** covers businesses and activities that Stripe generally will not support through Treasury—Stripe’s financial-account, money-movement, and card-issuing products—because of legal, regulatory, banking, sanctions, or elevated fraud/financial-crime risk.
The categories generally include:
- **Illegal goods or services**, including sanctioned activity
- **Adult content or services**
- **Gambling, betting, and lotteries**
- **Weapons, firearms, ammunition, and explosives**
- **Cannabis and other controlled substances**
- **Cryptocurrency and certain virtual-asset activities**
- **Money-services businesses**, such as money transmission, currency exchange, remittances, and some stored-value businesses
- **Lending, credit, debt collection, factoring, and other financial services**
- **Investment, brokerage, securities, and insurance activities**
- **Pharmaceuticals, medical products, and other regulated goods**
- **Crowdfunding, fundraising, and certain marketplace or payment-intermediary models**
- **Businesses involving government payments or other specially regulated activities**
The list is **not necessarily exhaustive**. Restrictions can depend on the business model, countries served, how customer funds move, the specific Treasury feature being used, and applicable law. A business that is allowed to use Stripe Payments may still be ineligible for Treasury.
Stripe’s current requirements and restricted-business categories are documented in its **Treasury requirements/restricted businesses** documentation, and Stripe may require additional review or decline an account even where an activity is not expressly listed. It states that the restricted-business categories are not exhaustive, matching the source’s key point. |
| CORRECT | Stripe’s **Treasury for platforms** restricted-business rules cover the types of businesses and practices that may not be eligible to receive Treasury financial accounts. The list is **representative, not exhaustive**, and eligibility can vary by financial-services provider and region.
### Prohibited businesses
These generally cannot use Treasury, including:
- Adult, escort, and dating services
- Arms trading
- ATMs
- Bail bonds
- Casinos, gambling, and gaming
- Debt collection, debt relief, and credit repair
- Door-to-door sales
- Government entities
- Direct hemp or marijuana businesses
- Illegal drugs
- Money services and currency exchange
- Payable-through accounts
- Payday lending and tax-anticipation programs
- Peer-to-peer payment businesses
- Shell corporations
- Certain telecommunications or surveillance-equipment providers
- Predatory or deceptive practices, including pyramid schemes and some MLM
- Unregistered charities
- Warranties and lifetime guarantees
### Restricted businesses
These may be considered only after enhanced review and, in some cases, explicit Stripe approval. Examples include:
- Insurance, investment, brokerage, and commodities businesses
- Lending, cash advances, and high-interest lending
- Money-services businesses
- Pharmaceuticals and tobacco
- Student-loan assistance
- Buy-now-pay-later providers
- Direct marketing and telemarketing
- Import/export and freight transport of physical goods
- Jewelry, gemstones, and precious-metals dealers
- Marketplaces
- NGOs
- NFTs and virtual-asset service providers
- Lawyers, accountants, and other professional-service providers
- Pawnshops and secondhand shops
- Sweepstakes businesses
- Third-party payment processors
- Vitamin and supplement sellers
Stripe also prohibits illegal products or services outright and restricts activity connected directly or indirectly with certain high-risk jurisdictions. Treasury is intended for **B2B use cases**, not consumer financial accounts.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements). It states that the categories are representative rather than exhaustive, matching the source. site:stripe.com restricted businesses Treasury Stripe list restricted businesses Treasury5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe’s **Prohibited and Restricted Businesses** list is a broad compliance screen for businesses using Stripe services, including Treasury. It covers:
- **High-risk jurisdictions and sanctioned persons**
- **Illegal products or services**, including illegal drugs, violence, counterfeit goods, IP infringement, and illegal weapons
- **Adult content and services**
- **Gambling and prize-based games**
- **Certain financial activities**, such as money transmission, lending, escrow, investment services, currency exchange, and bank-account funding
- **Cannabis and certain CBD products**
- **Cryptocurrency, NFTs, and stored-value products**
- **Pharmaceuticals, medical devices, telemedicine, tobacco, firearms, and weapons**
- **Crowdfunding, fundraising, dating, cyberlockers, and content platforms**
- **Travel businesses**, including some charter-air and travel-reservation services
- **Deceptive, predatory, or misleading business practices**
- **Third-party payment aggregation or processing on behalf of undisclosed merchants**
- **Country-specific categories**, which vary by jurisdiction
“**Prohibited**” means Stripe generally won’t support the activity. “**Restricted**” means it may be supportable only after additional due diligence, licensing checks, and sometimes explicit approval; approval can be limited to a particular Stripe product and may be withdrawn.
For **Treasury**, the list should be treated as an initial screen rather than a guarantee of eligibility. Treasury also has additional requirements imposed by Stripe’s banking partners and financial-regulatory obligations. The list is expressly representative—not exhaustive—and the applicable rules depend on your country, business model, customers, funds flows, and the specific Treasury product.
[Stripe’s list of Prohibited and Restricted Businesses](https://stripe.com/legal/restricted-businesses) It states that the Treasury restricted-businesses list is representative rather than exhaustive, matching the source. site:stripe.com/docs/treasury restricted businesses Stripe Treasury list covers0 results
results as cached 2026-08-24T07:04 Stripe Treasury restricted businesses list restricted businesses for Treasury5 results
results as cached 2026-08-24T07:04 opened 3 pages
|
| CORRECT | Stripe’s **Treasury restricted-business list** covers businesses and practices that may be **prohibited outright or allowed only after enhanced due diligence and explicit Stripe approval**. The list is representative, not exhaustive, and eligibility can vary by country, financial-services provider, and Treasury product.
For **Treasury for Platforms**, it broadly covers:
### Prohibited businesses
These generally cannot use Treasury:
- Adult, escort, or dating services
- Arms trading
- ATMs
- Bail bonds
- Casinos, gambling, and gaming
- Debt collection, debt relief, or credit restoration
- Door-to-door sales
- Government agencies and entities
- Direct hemp or marijuana businesses
- Illegal drugs
- Money services and currency exchange
- Payable-through accounts
- Payday lending and tax-anticipation programs
- Person-to-person payment businesses
- Shell corporations
- Telecommunications or surveillance-equipment providers
- Unfair, predatory, or deceptive practices, including pyramid schemes and certain MLMs
- Unregistered charities
- Warranties and lifetime guarantees
Illegal products or services are **never eligible**.
### Restricted businesses requiring enhanced review
Examples include:
- Insurance
- Investments, commodities, and brokerage
- Lending and cash advances
- Money-services businesses and currency exchange
- Pharmaceuticals
- Student-loan assistance
- Tobacco
- Buy-now-pay-later services
- Direct marketing and telemarketing
- Import/export and freight transport
- Jewelry, precious metals, and gems
- High-interest lenders
- Marketplaces
- NGOs
- NFTs and virtual-asset businesses
- Lawyers and accountants
- Pawnshops and secondhand shops
- Sweepstakes businesses
- Third-party payment processors
- Vitamins and supplements
Treasury also has separate requirements: it is intended for **B2B use cases**, not consumer financial accounts; certain high-risk jurisdictions are prohibited; and businesses owned by politically exposed persons are not eligible. Stripe makes the final decision during onboarding and may impose additional restrictions or withdraw approval. It states that the categories are representative rather than exhaustive and that some businesses may be allowed with Stripe approval, consistent with the source. site:stripe.com restricted businesses Treasury Stripe list restricted businesses Treasury5 results
results as cached 2026-08-24T07:04 opened 3 pages
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
19 Businesses and business practices in the following categories are either [restricted or prohibited](https://stripe.com/restricted-businesses) from using Treasury for platforms. Financial network rules, the requirements of our financial services providers, and our own compliance and legal obligations determine whether Stripe can provide financial services. In some cases, a business in one of these categories can use Treasury for platforms after getting explicit approval from Stripe. The type of businesses listed below are representative of our Restricted Businesses, but this list isn’t exhaustive. The specifics might vary depending on the financial service provider.
20 #### Warning
21 Businesses that offer illegal products or services are never eligible to use Treasury for platforms.
22 ### Prohibited business types
23 The businesses and business practices in the following categories are prohibited and can’t use Treasury for platforms:
| CORRECT | Businesses that sell **illegal products or services are not eligible for Stripe Treasury**. There is no set of additional requirements that makes an illegal-product business eligible.
In practice:
- The business and its products must comply with applicable laws and Stripe’s **Prohibited and Restricted Businesses** policy.
- A platform cannot use Stripe Treasury to provide financial accounts or payment services to connected accounts that sell prohibited or unlawful goods.
- Stripe may reject onboarding, require removal of the connected account, suspend services, or close accounts if it discovers illegal activity.
- The platform remains responsible for screening and monitoring its connected accounts, including KYC/KYB, sanctions screening, transaction monitoring, and compliance with applicable laws.
- Products that are legal but highly regulated or restricted—such as certain financial, pharmaceutical, weapons, cannabis, or adult-related products—may require specific approval and still may not be supported.
If “illegal” means illegal only in a particular country or state, the business generally still cannot use Stripe Treasury for transactions or activity that violate applicable law. The platform should obtain Stripe’s written compliance determination before onboarding any borderline business; approval is discretionary and not guaranteed. It states that businesses selling illegal products or services are not eligible for Stripe Treasury, matching the source’s requirement that they are never eligible. |
| CORRECT | Businesses that sell illegal products are **not eligible** to use Stripe Treasury for platforms.
In practice:
- The business and its products/services must comply with all applicable laws and Stripe’s **Prohibited and Restricted Businesses** policy.
- Stripe may reject or suspend a connected account if it sells goods or services that are illegal in any relevant jurisdiction, including controlled or illicit goods.
- A platform cannot use Treasury or Connect to bypass Stripe’s restrictions—even if the business passes KYC/KYB verification.
- The platform remains responsible for monitoring connected accounts and preventing prohibited activity.
- Final eligibility is determined by Stripe and its financial partners and may also depend on the business’s location, industry, licensing, AML/sanctions checks, and transaction model.
See Stripe’s current policy for the controlling list: [Stripe Restricted Businesses](https://stripe.com/legal/restricted-businesses). It states that businesses selling illegal products are not eligible to use Stripe Treasury for platforms, matching the source. |
| CORRECT | Businesses that sell illegal products are **not eligible** for Stripe Treasury for platforms.
Stripe requires platforms and their connected accounts to:
- Operate lawful businesses and comply with all applicable laws and regulations.
- Avoid Stripe’s prohibited or restricted businesses and activities.
- Provide accurate business, ownership, product, and compliance information.
- Pass Stripe and its financial-partner onboarding, KYC/KYB, sanctions, and risk reviews.
- Use Treasury accounts only for permitted business activities.
A product being legal in one jurisdiction does not necessarily make the business eligible if it is illegal where the business, customer, platform, or financial activity is located. Stripe may also reject businesses selling highly regulated products even when those products are technically legal, unless Stripe specifically supports them and the business has the required licenses.
There is no Treasury eligibility path or platform structure that permits processing for an otherwise illegal business. The platform may also be responsible for ensuring that its connected accounts comply. For a borderline or regulated business, the appropriate step is to disclose the activity to Stripe and request a compliance determination before onboarding. It states that businesses selling illegal products are not eligible for Stripe Treasury for platforms, matching the source. |
| CORRECT | Businesses that sell **illegal products or services are never eligible** to use Stripe Treasury for platforms.
Stripe also lists these prohibited categories, which cannot use Treasury for platforms:
- Illegal drugs and services
- Adult, escort, or dating services
- Arms trading
- Casinos, gambling, or gaming
- Hemp or marijuana direct businesses
- Money services and currency exchange
- Payday lending
- Bail bonds
- Debt collection, relief, or credit restoration
- Door-to-door sales
- Unregistered charities
- Shell corporations
- Predatory or deceptive practices, including pyramid schemes
- Certain telecommunications or surveillance equipment providers
Some regulated or higher-risk businesses—such as pharmaceuticals, tobacco, lending, marketplaces, and virtual-asset businesses—may be eligible only after enhanced review or explicit Stripe approval. Stripe’s review ultimately determines eligibility, and the list may vary by financial service provider and region. It states that businesses selling illegal products or services are never eligible to use Stripe Treasury for platforms, matching the source. site:stripe.com Treasury for platforms eligibility requirements illegal products businesses5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Businesses that offer **illegal products or services are never eligible** to use **Stripe Treasury for platforms**. There is no enhanced-review or explicit-approval pathway for this category.
Stripe lists examples of prohibited businesses, including:
- Illegal drug products and services
- Arms trading
- Gambling or casinos
- Adult, escort, or dating services
- Money services and currency exchange
- Bail bonds
- Payday lending
- Deceptive or predatory practices
- Hemp or marijuana direct businesses
This applies even if the activity is legal in the business’s jurisdiction; Stripe’s Treasury eligibility and financial-partner requirements still govern. See Stripe’s [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements). It states that businesses offering illegal products or services are never eligible to use Stripe Treasury for platforms, matching the source. site:stripe.com Treasury for platforms eligibility requirements illegal products businesses5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Businesses that sell **illegal products or services are never eligible** to use **Stripe Treasury for platforms**. There is no approval or enhanced-review pathway for them.
Stripe’s requirements state that:
- Illegal products and services are categorically prohibited.
- The prohibition applies to the platform’s connected accounts, customers, and recipients.
- Platforms must offer Treasury-based financial services only to businesses that meet Stripe’s requirements and must have processes to identify and understand their customers’ businesses.
- Other restricted industries—such as pharmaceuticals, tobacco, lending, insurance, and virtual-asset services—may be considered only through enhanced review, but **illegal goods or services cannot be approved**.
See Stripe’s [Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements), particularly the “Prohibited and restricted business types” section. It states that businesses selling illegal products or services are never eligible for Stripe Treasury for platforms, matching the source. site:docs.stripe.com/treasury eligibility requirements prohibited businesses illegal products platforms1 result
results as cached 2026-08-24T07:04 Stripe Treasury for platforms eligibility requirements businesses illegal products5 results
results as cached 2026-08-24T07:04 Stripe services agreement prohibited businesses illegal products Treasury platforms5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
68 * Virtual asset service providers (VASPs)
69 ## Prohibited business addresses
70 Treasury for platforms only supports connected accounts with a valid US-based physical business. The address can’t be:
71 * Of or provided by a registered agent
72 * A PO box
| CORRECT | A connected account generally needs a **valid physical business address in the United States** for Stripe Treasury. It must be the business’s actual operating or legal address—not the platform’s address—and **PO boxes typically aren’t accepted**.
For the account record, provide:
- `company.address` for a company or nonprofit
- `individual.address` for a sole proprietor or individual
The address must match the connected account’s verification information and country eligibility. It states that the connected account needs a valid physical business address in the United States, matching the source requirement. |
| CORRECT | A connected account for **Stripe Treasury** must have a **valid physical business address in the United States**. It generally cannot be a **PO box or virtual mailbox**.
For a sole proprietor, this may be the owner’s physical residential address if that is the business’s actual address. The address should be provided in the connected account’s business/company information during Stripe onboarding. The answer states that the connected account needs a valid physical business address in the United States, matching the source. |
| CORRECT | A connected account using **Stripe Treasury for platforms must have a valid physical U.S. business address**.
- For a **company**, use its actual U.S. business address.
- For an **individual or sole proprietor**, use the owner’s U.S. residential address.
- **P.O. boxes, virtual offices, and mail-forwarding addresses generally aren’t accepted.**
The address should be provided in the connected account’s business/legal information during Stripe onboarding and must satisfy Stripe’s verification requirements. It states that the connected account must have a valid physical U.S. business address, matching the source. |
| CORRECT | A connected account must have a **valid, physical business address in the United States**.
The address cannot be:
- A registered-agent address
- A PO box
- A highway contract (HC) box
- A private mailbox
Stripe may take up to **24 business hours** to reflect business-address changes on incoming or outgoing wires. citeturn0search0 It states that the connected account needs a valid physical business address in the United States, matching the source. site:docs.stripe.com treasury platforms connected account business address business profile5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | A connected account needs a **valid, physical business address in the United States** for Stripe Treasury for platforms.
The address **cannot** be:
- A registered agent’s address
- A PO box
- A highway contract (HC) box
- A private mailbox
Stripe may take up to **24 business hours** to reflect business-address changes on incoming and outgoing wires. citeturn0search0 The answer states that the connected account needs a valid physical business address in the United States, matching the source. site:docs.stripe.com treasury platforms connected account business address requirements5 results
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | A connected account needs a **valid, physical business address in the United States**.
The address **cannot** be:
- A registered agent’s address
- A PO box
- A highway contract (HC) box
- A private mailbox (PMB)
This requirement applies to connected accounts using **Treasury for platforms**. Changes to the business address may take up to 24 business hours to appear on incoming and outgoing wires. It states that the connected account needs a valid physical business address in the United States, matching the source. site:docs.stripe.com treasury for platforms connected account business address requirement5 results
results as cached 2026-08-24T07:04 opened 1 page
|
Right either way — the model knows this, and checking confirms it. Unaided belief: correct. With tools: searched on 100% of samples, answered correctly on 100%.
75 Changes to business addresses might take up to 24 business hours to be reflected on outgoing and incoming wires.
76 ## Politically exposed persons
77 Stripe screens applications to identify any connected account user that’s a politically exposed person (PEP) including foreign senior political figures (SPF). Businesses that are owned by PEPs are prohibited from using Treasury for platforms services.
| CORRECT | For **Stripe Treasury for platforms**, a business is generally **not eligible if it is owned or controlled by a politically exposed person (PEP)**.
This typically includes a business where a PEP is:
- A beneficial owner—usually someone who directly or indirectly owns **25% or more**
- A controlling person or senior executive
- A close family member or close associate of a PEP, where Stripe’s compliance review treats that relationship as relevant
A PEP generally means someone who currently holds, or has held, a prominent public function—such as a senior government official, senior military or judicial official, senior political-party official, or executive of a state-owned enterprise.
Stripe may request ownership, control, identity, and source-of-funds information during onboarding. Meeting ordinary business requirements does not override the PEP restriction, and Stripe can decline or suspend Treasury access based on its compliance review. It states that businesses owned by a politically exposed person are not eligible for Stripe Treasury for platforms, matching the source's prohibition. |
| WRONG | Under Stripe Treasury for platforms, a business **owned or controlled by a politically exposed person (PEP) is generally not eligible** for a Treasury financial account.
In practice:
- The connected business must disclose its ownership and control information during onboarding.
- Stripe and its banking partners screen owners, directors, and controlling persons for PEP and sanctions status.
- A business may be declined if a PEP owns or controls it; meeting the other Treasury requirements does not override this restriction.
- This is separate from ordinary Stripe Payments eligibility—an account might be able to use some Stripe Payments products but still be ineligible for Treasury.
- Stripe may request additional information or apply restrictions based on the specific facts and the applicable country or banking partner’s rules.
Stripe’s eligibility rules can change, so the platform should confirm the current Treasury prohibited-business and eligibility requirements with Stripe before onboarding the business. It says PEP-owned or controlled businesses are generally not eligible and may be declined, whereas the source states that businesses owned by PEPs are prohibited from using Treasury for platforms services. |
| CORRECT | For **Stripe Treasury**, a business is generally **not eligible if it is owned or controlled by a politically exposed person (PEP)**. This can include:
- A person currently or formerly entrusted with a prominent public function
- The PEP’s immediate family members
- Known close associates of the PEP
The restriction may apply where the PEP is a beneficial owner, director, or otherwise exercises control—not only where the person owns 25% or more.
Because Treasury accounts are provided through banking partners, Stripe may apply enhanced due diligence and can decline or restrict the business even if the business is otherwise legitimate. PEP status by itself is not illegal, but it can make the business ineligible for Treasury under Stripe or its financial partners’ risk policies.
The platform should disclose any PEP connection during onboarding rather than attempting to omit or restructure the ownership information. Stripe’s current country-specific Treasury requirements and its review decision control, so the platform should confirm the case directly with Stripe before onboarding. It states that businesses owned or controlled by politically exposed persons are not eligible for Stripe Treasury, matching the source's prohibition on PEP-owned businesses. |
| CORRECT | According to Stripe’s **Treasury for platforms requirements**, businesses **owned by politically exposed persons (PEPs)** are **prohibited** from using Treasury for platforms services.
Stripe screens applications to identify whether any connected-account user is a PEP, including a **foreign senior political figure (SPF)**. The requirement is stated as an outright prohibition—not merely a category subject to enhanced review. The answer states that businesses owned by politically exposed persons are prohibited from using Stripe Treasury for platforms services, matching the source. site:docs.stripe.com treasury platforms politically exposed persons eligibility requirements business owners PEP1 result
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | According to Stripe’s **Treasury for platforms requirements**:
- Stripe screens applications to identify whether any connected-account user is a **politically exposed person (PEP)**, including a **foreign senior political figure (SPF)**.
- **Businesses owned by PEPs are prohibited from using Treasury for platforms services.**
Thus, a business with PEP ownership is not eligible for Treasury for platforms, rather than merely being subject to enhanced review. Stripe’s requirements page does not provide a stated ownership-percentage threshold or an exception process for PEP-owned businesses. It correctly states that businesses owned by politically exposed persons are prohibited from using Stripe Treasury for platforms services. site:docs.stripe.com treasury platforms politically exposed persons eligibility requirements businesses owned by PEPs1 result
results as cached 2026-08-24T07:04 opened 1 page
|
| CORRECT | Stripe Treasury for platforms prohibits businesses owned by politically exposed persons (PEPs) from using its services.
Stripe screens applications to identify whether any connected-account user is a PEP, including a **foreign senior political figure (SPF)**. If the business is owned by a PEP, it is **not eligible** for Treasury for platforms—there is no indication on the requirements page that enhanced review or approval can override this prohibition.
Source: [Stripe Treasury for platforms requirements](https://docs.stripe.com/treasury/connect/requirements) It correctly states that businesses owned by politically exposed persons are prohibited and therefore ineligible for Stripe Treasury for platforms services. site:docs.stripe.com treasury platforms eligibility politically exposed persons PEP business owners1 result
results as cached 2026-08-24T07:04 opened 1 page
|