# Mippo LaaS

## Docs

- [Get KYC status for a client onboarding submission](https://laas.mippo.io/docs/api-reference/kyc/status.md): Poll the current state of a KYC submission by kycToken to check whether the client is pending, approved, or rejected by the compliance provider.
- [Submit KYC data for compliance screening](https://laas.mippo.io/docs/api-reference/kyc/submit.md): Send end-user KYC and PEP data to run AML screening and sanctions checks on a client before enabling Pix to stablecoin transactions.
- [LaaS API overview: base URLs, versioning, and errors](https://laas.mippo.io/docs/api-reference/overview.md): Reference for the Mippo LaaS REST API covering base URLs, versioning, rate limits, request signing, and the shared error response format.
- [Apply as a Mippo LaaS partner](https://laas.mippo.io/docs/api-reference/partner/apply.md): Submit a partner application to onboard your company for the Mippo LaaS API, including legal entity details, contact info, and use case.
- [Confirm MFA for a pending transaction](https://laas.mippo.io/docs/api-reference/transactions/confirm-mfa.md): Submit the TOTP code from the end-user to clear the multi-factor authentication gate and continue a pending Pix to stablecoin transaction.
- [Initiate a Pix to stablecoin transaction](https://laas.mippo.io/docs/api-reference/transactions/initiate.md): Start a Pix to stablecoin transaction for an approved client by specifying the amount, destination wallet, and target chain and token.
- [Get status of a Pix to stablecoin transaction](https://laas.mippo.io/docs/api-reference/transactions/status.md): Poll the current state of a Pix to stablecoin transaction, including Pix receipt, on-chain transfer hash, and pending MFA or compliance gates.
- [Authentication with API keys and Clerk JWT](https://laas.mippo.io/docs/authentication.md): How partners authenticate server calls to Mippo LaaS with API keys and how the partner dashboard uses Clerk JWT for user session tokens.
- [Compliance obligations for LaaS partners](https://laas.mippo.io/docs/guides/compliance.md): BCB SPSAV rules, Travel Rule requirements, KYT monitoring, and record retention obligations that partners must follow when integrating Mippo LaaS.
- [LaaS KYC onboarding models and transaction flows](https://laas.mippo.io/docs/guides/models.md): Compare Mippo LaaS KYC/AML models — Direct Onboard, Client via Partner, and Shared Onboard — with sequence diagrams and Pix settlement flows.
- [Webhooks for LaaS transaction and KYC events](https://laas.mippo.io/docs/guides/webhooks.md): Receive real-time notifications for KYC status changes, transaction lifecycle events, and settlement callbacks with signed webhook payloads.
- [Introduction to Mippo LaaS for Pix and stablecoins](https://laas.mippo.io/docs/introduction.md): Embed compliant Pix to stablecoin flows in your app using Mippo BCB SPSAV license, KYC screening, and settlement APIs built for LaaS partners.
- [Quickstart: your first Pix to stablecoin transaction](https://laas.mippo.io/docs/quickstart.md): Set up API keys, submit KYC for a test client, and process your first Pix to stablecoin transaction with the Mippo LaaS API in under 5 minutes.
- [TypeScript SDK for the Mippo LaaS API](https://laas.mippo.io/docs/sdk/typescript.md): Install and use @mippo/laas-sdk, the typed TypeScript client for the Mippo LaaS API covering KYC, transactions, and webhook signature verification.