KymoPay Legal Policies
Read before publishing
These are drafts for KymoPay (a product of PayAiro Inc.) and need review by a US fintech lawyer before they go live on Google Play or the App Store. Text in [brackets] is a placeholder to fill or confirm.
Blocker to resolve first: Dakota's public Terms of Service say the Dakota account is for the customer's "internal business purposes" only and "cannot be used for personal, consumer, or household purposes". Its Funds Transfer Agreement also bars using the service for third parties. A consumer P2P app needs a separate platform or embedded-finance agreement with Dakota that allows end users. Confirm PayAiro has one. These drafts assume it does.
What the partners require, and where it lands
| Partner requirement | Source | Reflected in |
|---|---|---|
| Say Dakota Ridge, Inc. is a fintech company, not a bank; regulated payment services come from Dakota Platform, Inc. (NMLS #2727274) and partner banks | Dakota licenses | ToS 3, Fund Transfer 2 |
| Only offer transfers where Dakota is licensed; Dakota Platform lists 20 approved states (no CA, NY or TX) | Dakota licenses | ToS 2, Fund Transfer 2 |
| Bank transfers run through Lead Bank (Missouri); transfers cannot be cancelled once initiated | Funds Transfer Agreement | Fund Transfer 5 |
| Report errors within 30 days, unauthorized ACH within 2 business days, suspected fraud within 24 hours | Dakota Terms 2.5, 2.6; Funds Transfer 8 | Fund Transfer 8, 9 |
| Dakota may reject, hold, reverse or freeze transfers for fraud, sanctions or legal orders | Dakota Terms 2.4; Funds Transfer 4 | Fund Transfer 6, 7 |
| No OFAC-listed parties, prohibited jurisdictions, VPN evasion or Dakota-prohibited businesses | Dakota Terms 1.3, 1.4 | ToS 9, Content Policy 3 |
| Stablecoin risk: volatility, loss, irreversibility; not legal tender; not FDIC-insured; FDIC covers only USD at partner banks up to $250,000 | Dakota Terms 12.2 to 12.4 | ToS 8, Fund Transfer 10 |
| Users agree to partners' terms, privacy policies and E-Sign notice | Dakota Terms 4.1; E-Sign notice | ToS 3, 4 |
| Collect and verify identity (USA PATRIOT Act s.326) | Dakota Terms 12.1 | ToS 5, Privacy 2 |
| Disclose Stripe's processing; Stripe is a processor for KymoPay, and a controller for its own fraud and compliance uses | Stripe Privacy Policy | Privacy 4 |
Open items
- Confirm PayAiro's Dakota agreement allows consumer end users (blocker above).
- Decide launch states. Dakota's 20 approved states exclude Texas, where PayAiro is based. Either geo-restrict KymoPay or confirm PayAiro or another partner holds licences elsewhere.
- Confirm exactly what Stripe does in KymoPay (card funding, identity checks, on-ramp, or Bridge) so the policies name the right Stripe product.
- Confirm which stablecoins are supported (USDC, Dakota's Reserve Dollar, other) and whether wallets are custodial or self-custody.
- Fill KymoPay's support email, website, effective date and fees.
- Check app-store crypto rules: Google Play requires US crypto exchanges and custodial wallets to be FinCEN-registered or licensed; Apple requires crypto apps to come from properly licensed entities.
- If Coinme's services are used in KymoPay, add the disclosures in Exhibit A s.5 of the Coinme agreement. Its s.1.10 also requires Coinme's consent before naming Coinme publicly.
- Use Stripe's US privacy policy link (stripe.com/privacy) for US users, not the India version.
- Ask counsel whether Regulation E (consumer electronic fund transfer rules) applies to KymoPay. Dakota says its business service is outside Reg E, but a consumer app may not be.
- Confirm Lead Bank is the bank partner under PayAiro's own Dakota agreement, and get the real ACH, FedNow and wire cut-offs, timings, limits and hold days.
- Make the Google Play Data Safety form and Apple privacy labels match Privacy Policy section 2 exactly.
- Build in-app Report and Block buttons before submission. Apple requires them for apps with user content, and the Content Policy promises them.
- Have counsel check whether a GLBA privacy notice and state-specific disclosures (for example California or Texas) are required.