> ## Documentation Index
> Fetch the complete documentation index at: https://docs.swipelux.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Methods

> Supported Swipelux pay-in and payout rails, including SEPA and Faster Payments open banking, card acquiring, crypto deposits, and third-party aggregators.

## Payment Methods

Swipelux orchestrates multiple settlement rails for pay-ins and payouts.

### Supported Pay-in Methods

1. **Fiat deposits (User -> Swipelux)**
   * Open Banking: Instant SEPA / Faster Payments
   * Card Acquiring: Visa/Mastercard (subject to MCC restrictions)

2. **Crypto deposits (User -> Swipelux)**
   * Users may deposit supported assets such as USDC directly into their segregated MPC wallet. Wallets are screened by a third-party service provider.

3. **Third-Party Aggregators**
   * Swipelux supports orchestrated settlement from licensed third-party partners. Swipelux acts as the wallet provider and final settlement agent in these flows.

For implementation guidance, see [receive funds](/integration/receive-funds).

### Supported Payout Methods

**Fiat Payouts (Swipelux -> User)**

* **Flow:** Stablecoin -> Swipelux Liquidity -> Fiat Conversion -> User Bank Account
* **Rule:** Payouts can only be sent to a bank account in the exact legal name of the verified KYC user. Third-party payouts are not supported in this flow.

The exact-name restriction above applies to this direct-user bank payout flow. It does not replace the separate v3 recipient-destination flow described in [Recipients](/integration/recipients).

For implementation guidance, see [send funds](/integration/send-funds).


## Related topics

- [Swipelux compliance reference](/knowledge-base/compliance/overview.md)
- [Errors and retries](/integration/errors.md)
- [Capabilities and tasks](/integration/onboarding/capabilities-and-requirements.md)
- [Create account](/api-reference/accounts/post-v3-customers-by-customer-id-accounts.md)
- [Migrate a v1 or v2 integration to Swipelux API v3](/api-reference/versioning/migrate-to-v3.md)