Conduit Meeting Prep
Alignment of Payapp to app.conduit.financial (API v2) — questions, agenda, and rollout plan.
Payapp (payapp.one) is a self-serve business banking product for small and medium businesses that need a named USD account to receive deposits and pay out to vendors, contractors, and partners. Businesses sign up online, complete KYB, get provisioned a USD virtual account, receive incoming deposits, and send outgoing payments — all through a single API-driven platform.
Core flows we need
- • Business onboarding & KYB (self-serve, no SSN sent to partner)
- • USD virtual account provisioning with deposit instructions
- • Inbound deposits (ACH, same-day ACH, Fedwire, RTP)
- • Outbound payouts (ACH / wire / local rails)
- • Real-time balance & full transaction history
- • Platform fee taken on incoming deposits
Customer profile & scale
- • SMBs: LLCs, sole proprietors, partnerships, corporations
- • USD-first; EUR/GBP/SEPA in a later phase
- • Tiered transfer-limit packages (daily/weekly/monthly)
- • Growing merchant base onboarded via self-serve flow
Why Conduit
We need a partner where payouts are fully enabled, full virtual-account transaction history is available via API, in-flight payments can be cancelled, and balances update through webhooks rather than a sync job that overwrites manual overrides. Conduit's application-based onboarding, named virtual accounts, and multi-rail pay-in/pay-out match our product model directly.
Edit the volume figures above to reflect your actual expected monthly onboarding and transaction volume before the call.
- •Withdrawal/payout API returned 403 (feature disabled on partner account).
- •Virtual account history endpoint returned 403 — full transaction visibility lost.
- •No cancellation endpoint for in-flight (settling) ACH payments.
- •Balance sync overwrote manually-set balances for special accounts.
- •Static onboarding links expired, breaking KYC for users mid-flow.
| Payapp (current) | Conduit equivalent | What changes |
|---|---|---|
| KYC link (static, expires) | Application model: submit → webhook application.approved → customer auto-created | No expiring links; no polling |
| KYB submission (base64 docs, SSN stored locally only) | Per-country KYB requirements + document upload + application submit | Confirm no SSN required |
| Virtual account provisioning (USD, First Premier) | Virtual Accounts scoped to customer + asset; states pending_activation→active→disabled; us_domestic (ACH/Fedwire/RTP) + swift | Richer rails out of the box |
| Deposit crediting (manual PendingDeposit → credit) | Inbound deposit → webhook transaction.* → balance update | Move to webhook-driven auto-credit |
| Withdrawal / send money (manual; Paywint API 403) | Payouts: fiat via SWIFT/SEPA/local rails; crypto via non-custodial wallets | Confirm payout API enabled |
| Platform fee on deposits (2% + admin fee, swept) | Charge-a-fee-on-a-deposit: margin on funding order OR sweep from balance | Pick a pattern with Conduit |
| Transaction history (list-pw-transactions 403) | Customer-scoped transaction reads + webhooks transaction.* | Restore real history visibility |
| Kill-switch / on-hold / fraud-closure | No partner-side pause; we gate before calling payout | Keep our kill-switch at app layer |
| Balance sync overwrites manual balances | Conduit balance = source of truth via webhooks | Decide trust vs. manual override |
- 1Payouts enabled? Is the payout API fully enabled for our account type in production (the feature that was 403 on our previous partner)?
- 2Transaction history API — reliable list/get for virtual-account deposits + payouts, full history, no feature gating?
- 3Cancellation — can we cancel an in-flight payout (settling/pending)? Which states allow cancellation?
- 4Same-day ACH / RTP / Fedwire — available on us_domestic virtual accounts? Per-rail limits or costs?
- 5KYB without SSN — can business onboarding complete with EIN + formation docs only (no owner SSN transmitted)?
- 6KYC reliance — can our existing IDV results satisfy control-person verification (avoid re-running KYC)?
- 7Fee/margin on deposits — recommended pattern (margin-on-funding-order vs. balance sweep)?
- 8Webhook reliability + sandbox — deterministic deposit/withdrawal/payout scenarios? Retry policy + max latency?
- 9Onboarding SLA — automated review time; manual-review triggers we should pre-empt?
- 10Multicurrency — USD-only now; EUR/GBP/SEPA scope and any extra KYB per currency?
Our product & current pain
Self-serve onboarding, USD virtual accounts, deposits, payouts, tiered limits, fee-on-deposit; gaps that forced us off our previous partner (payout 403, history 403, no cancel, balance-sync clobbering manual balances).
Conduit model walkthrough
Application-based onboarding, webhooks, virtual accounts, payouts, signing modes.
Capability fit
Walk the alignment map; confirm payouts enabled, history API, cancellation, same-day rails.
Compliance & data
KYB-without-SSN, KYC reliance, document formats, fraud-closure handling.
Fees & commercial
Fee-on-deposit pattern, margin, pricing, sandbox access.
Sandbox + integration plan
Sandbox keys, webhook endpoint (paynexpay.base44.app/functions/conduitWebhook), phased rollout.
Phase 0 — Sandbox
API key, register webhook endpoint, run quickstart (first transaction.completed webhook).
Phase 1 — Onboarding
Replace KYC-link flow with application submit → webhook approval; keep SSN local.
Phase 2 — Virtual accounts
Provision USD VAs, render us_domestic + swift deposit instructions.
Phase 3 — Deposits + history
Webhook-driven auto-credit + transaction history reads (replaces manual tracking).
Phase 4 — Payouts
Wire Send Money → Conduit payout API; reintroduce automated withdrawals.
Phase 5 — Fee sweep
Platform fee on deposits (margin/sweep); tiered limits map to Conduit constraints.
Webhook endpoint to share: https://paynexpay.base44.app/functions/conduitWebhook