Instant cash-out feasibility (post-M5)

[Hazyshades]

Outcome

Decide whether Sendly can offer Instant bank cash-out after a zkTLS claim, and under what legal and operational conditions. Record Circle CPN as a candidate, not as a selected integration.

Context

M5 proves embedded USDC funding only (#45). Instant cash-out is the next pilot candidate: after a zkTLS claim, the recipient receives a verifiable payout to a bank account.

Circle describes direct bank payouts through CPN partners. Participation requires a separate legal-entity, licensing, and operational review (Circle CPN). Do not treat documentation marketing as approval for Sendly.

Questions to answer

• Can Sendly act as a Circle CPN client directly, or must Sendly work through an existing network participant?
• Which countries and bank-detail formats are in scope for a first Instant pilot?
• How are quote, payout, refund, and failure states exposed to Sendly?
• Who holds customer funds during payout, and who owns AML or sanctions checks?
• How does the payout operation bind to the claimed zkSEND payment and the authenticated recipient?
• What sandbox or limited environment exists before any production payout?

Acceptance criteria

• A written decision names CPN as candidate, selected partner, or rejected for the first Instant pilot, with sources and date checked.
• Direct-client versus network-participant path is explicit.
• Country list, bank-detail requirements, quote, payout, refund, and funds-responsibility answers are recorded or marked unknown.
• Instant cash-out remains blocked until legal and operational checks pass.
• No production bank payout is enabled from this spike alone.
• M6 row approval (M6: Mainnet Launch Gate #62) remains required for any mainnet Instant enablement.
• Wise or other P2P rails are out of scope for this Instant feasibility issue.

Dependencies

• M5 embedded funding gate (M5: Embedded USDC Funding Pilot release gate #45) can proceed without waiting on this issue.
• Any later Instant pilot needs its own corridor, adapter, and UX issues after this feasibility pass.

Non-goals

• No CPN production integration in this issue.
• No P2P maker escrow work here.
• No change to M5 on-ramp scope.

[Hazyshades]

Follow-up after M5 embedded funding. Parent gate: #45.