Card Payment Settlement & Payout Flow
1. Secure Card Payment Processing
The payment is handled through Suby’s card payment orchestration layer, which relies exclusively on regulated and PCI DSS–compliant infrastructure. Sensitive card information is processed directly by certified providers and never transits through Suby’s systems.
2. Payment Settlement
Once authorized, the payment enters the settlement phase. At this stage, the transaction is finalized through regulated payment rails, ensuring compliance with card-network and financial regulations.
3. Fiat-to-USDC Conversion
During settlement, the fiat amount collected from the card payment is converted into USDC. This conversion occurs within a regulated settlement and conversion layer, allowing Suby to provide stable, dollar-denominated payouts while avoiding exposure to fiat banking complexity.
4. Payout Preparation & Aggregation
Converted funds are then aggregated for payout. Aggregation helps optimize payout efficiency, reduce operational costs, and align payout timing with the merchant’s selected pricing plan.
5. Direct Wallet Payout
Payouts are sent directly to the Merchant’s self-custodial wallet, which remains fully owned and controlled by the Merchant at all times. Suby does not act as a custodian and does not store or hold Merchant funds. Suby may facilitate payout orchestration, including batching or timing of settlements.
6. Payout Timing
Payout frequency (for example, every 5 to 15 days) depends on the merchant’s pricing plan and configuration. Once a payout is executed, funds arrive directly in the merchant’s wallet.
7. Final Settlement
All card payment payouts are settled in USDC (USD Coin) and sent directly to the wallet you have configured in your settings, on Base or Solana. This provides price stability, transparency, and global accessibility.
Key Payment & Risk Principles
Suby does not store or process card data
Card payments rely on regulated, PCI DSS–compliant infrastructure
Payout timing is independent from any rolling reserve
Payout frequency (e.g. every 5 to 15 days) depends on the merchant’s pricing plan
Payouts are sent directly to merchant-owned wallets
Rolling Reserve (when applicable)
In specific cases, a rolling reserve may be applied for risk or compliance reasons
A rolling reserve is separate from payout scheduling
The reserve amount and duration depend on the nature of the business, transaction volume, and risk profile
Reserved funds are released according to predefined conditions
