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

# Partner FAQs

> Find answers to common Houdini partner questions about tiers, commissions, monitoring, support, API features, compliance, risk and security.

## Tiers, Commission & Monitoring

> [accordion] How do I get Pro tier?
>
> All accounts start on Free. Pro comes with higher rate limits, which can be customized per agreement.
>
> Upgrades are handled manually. Contact the Houdini team through the [Partner Portal](https://app.houdiniswap.com/partner/dashboard) to request one.
>
> See: [Rate Limits & Tiers](https://docs.houdini.com/developer-hub/getting-started/rate-limits-and-tiers.md)

> [accordion] How are payouts handled, in which tokens, and how often do they occur?
>
> Commissions are paid in **USDC**.
>
> Earnings accumulate automatically as eligible swaps settle and are reflected in:
>
> * Commission Balance
> * Withdrawable Balance
>
> Withdrawals are initiated manually by the partner through the dashboard. There is no automatic payout schedule. Funds are available for withdrawal once reflected as withdrawable.
>
> See: [Analytics & Settlement](https://docs.houdini.com/analytics-and-settlement.md)

> [accordion] Can we monitor our volume and collected fees in real time?
>
> The [Partner Dashboard](https://app.houdiniswap.com/partner/login) displays:
>
> * All-time volume
> * Swap count
> * Commission balance
> * Withdrawable balance
> * Daily and monthly charts
>
> The same data is available via API through the [Partner Stats](https://docs.houdini.com/developer-hub/core-concepts/partner-stats.md) endpoints.
>
> See: [Analytics & Settlement](https://docs.houdini.com/analytics-and-settlement.md)

## Operational & Support

> [accordion] What should be done if a user's transaction gets stuck?
>
> A stuck transaction can have multiple causes, including:
>
> * Network congestion
> * Liquidity provider maintenance
> * Compliance review
> * Routing delays
>
> **Recommended process:**
>
> 1. Confirm the transaction hash and Order ID.
> 2. Check order status via the status endpoint.
> 3. If the issue is not resolved automatically, escalate to Houdini support with the Order ID.
>
> Partners may choose one of two models:
>
> * Redirect users directly to Houdini support.
> * Handle first-line support internally and escalate cases to Houdini when needed.

> [accordion] How quickly are transaction-related issues resolved?
>
> Resolution time depends on the underlying cause:
>
> * Network congestion: typically minutes
> * Liquidity provider maintenance: minutes to hours
> * Compliance review: case-dependent
>
> There is no fixed SLA for all scenarios. Critical partner escalations are handled through direct communication channels.

## Product Scope & Customization

> [accordion] Is Split available at the API level?
>
> Yes. You can create and manage multiple swaps in a single batch, using CEX or private routing, through the Partner API.
>
> See: [Split](https://docs.houdini.com/developer-hub/swap-flows/split.md)

> [accordion] Can we randomize the CEXes used for private swaps at the API level?
>
> Yes. API partners can enable **route rotation** for private swaps.
>
> When rotation is enabled:
>
> * The route used for the previous user is excluded from selection.
> * The routing engine selects the next best available route.
> * Selection is constrained by a configurable price deviation threshold defined in the API request.
>
> If no alternative routes exist within the defined deviation threshold, the original route is returned to the rotation pool and routing continues normally.
>
> This ensures:
>
> * Users are not consistently routed through the same execution path.
> * Pricing remains within acceptable limits defined by the partner.
>
> See: [Payout Wallet Rotation](https://docs.houdini.com/developer-hub/core-concepts/payout-wallet-rotation.md) and [Routing Types](https://docs.houdini.com/developer-hub/core-concepts/routing-types.md)

> [accordion] Can we add new assets ourselves using the Houdini API?
>
> Asset and network support is managed by Houdini. If additional tokens or chains are required, contact the team to request integration.
>
> See: [Tokens & Networks](https://docs.houdini.com/developer-hub/core-concepts/tokens-networks.md)

## Risk & Compliance

> [accordion] How does the integration model work?
>
> Partners integrate through the Houdini Partner API:
>
> * **Partner:** builds the UI and sends API requests.
> * **Exchange providers:** execute the swap, run AML/KYT screening, hold funds while the swap is in progress, and issue refunds.
> * **Houdini:** non-custodial. Handles routing, orchestration, order records and user support.
>
> Request does not have a partner API yet. It is on the roadmap and is currently available only in the Houdini web app.

> [accordion] Does Houdini conduct independent transaction screening, or is compliance fully handled by the CEXs?
>
> Houdini is a non-custodial liquidity aggregator. We do not pool funds and we do not operate mixer contracts.
>
> Compliance enforcement is built into the routing perimeter and executed through vetted exchange partners:
>
> * Primary screening is performed by execution partners at the deposit stage using real-time AML/AFT screening tools.
> * Houdini maintains a strict partner due diligence process (KYB requirements, compliance officers and policies, law enforcement cooperation).
> * Houdini also enforces structural safeguards such as transaction limits, geo restrictions and sanctioned-address checks at the API level.
>
> See: [Privacy and Compliance](https://docs.houdini.com/overview/getting-started/privacy-and-compliance.md)

> [accordion] How does AML screening work across both legs of a private swap?
>
> Each provider runs its own KYT screening on the funds it receives:
>
> * **Exchange 1** screens the original sender wallet and source asset.
> * **Exchange 2** screens the funds it receives from the first leg.
>
> Houdini keeps the full order record, linking both legs, the source wallet and the transaction hashes. This record is provided to providers or authorities through valid legal or compliance request processes, so the full path stays traceable end-to-end.

> [accordion] Is KYC required?
>
> No upfront KYC. The model is **KYT first**: deposits are screened on-chain as they arrive.
>
> KYC and enhanced due diligence (EDD) are triggered only when risk is flagged. The provider that flagged the transaction collects and verifies the user's information.

> [accordion] How are failed or flagged transactions refunded?
>
> If a deposit is flagged, the provider asks the user to complete KYC:
>
> * If the user passes, the swap goes ahead.
> * If not, the provider refunds the funds, less network fees.
>
> The provider holding the funds at the time of failure is responsible for the refund. Houdini's 24/7 support team coordinates refunds with the user.

> [accordion] What happens if a bad actor is involved in a swap, and who is responsible?
>
> If a deposit is linked to sanctioned wallets or illicit activity, the provider holding the funds applies its own AML policy under its compliance obligations and applicable law. Depending on the case, it may:
>
> * Hold the funds
> * Request KYC/EDD
> * Refund the funds
> * Freeze and report the funds where required by law
>
> Houdini never takes custody of user funds. Houdini's role is to ensure swaps route only through compliant partners and to enforce platform-level safeguards, including:
>
> * Partner oversight and continuous review
> * Transaction limits
> * Blocking access from restricted jurisdictions
> * Rejecting sanctioned destination addresses at the API level (`422 ADDRESS_TO_SANCTIONED`)
>
> Responsibility and handling procedures are further defined in the partner agreement.
>
> See: [Privacy and Compliance](https://docs.houdini.com/overview/getting-started/privacy-and-compliance.md) and [Error Codes & Troubleshooting](https://docs.houdini.com/developer-hub/troubleshooting/error-codes-and-troubleshooting.md)

> [accordion] How do Houdini private swaps comply with US jurisdiction?
>
> Houdini applies perimeter controls designed to prevent usage from restricted jurisdictions:
>
> * Access from the US and EU sanctioned countries is blocked on the website.
> * Private swaps route through vetted partners that maintain internal auditability and comply with lawful requests.
>
> API partners must ensure their own distribution complies with applicable laws and must pass the required compliance signals through request headers.
>
> See: [Privacy and Compliance](https://docs.houdini.com/overview/getting-started/privacy-and-compliance.md) and [API Keys & Authentication](https://docs.houdini.com/developer-hub/getting-started/authentication.md#mandatory-compliance-headers)

## Security & Audit

> [accordion] Why hasn't Houdini been audited yet, while competitors such as Li.Fi and 1inch have been audited?
>
> Houdini is currently in the process of obtaining **SOC 2 certification with Deloitte**, focused on security, availability, and operational controls.
>
> For detailed security documentation or enterprise discussions, contact the Houdini team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.