> For the complete documentation index, see [llms.txt](https://docs.apacx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apacx.io/xafer-waas/xafer-waas/integration-and-onboarding.md).

# Integration & Onboarding

### API Documentation

Use Xafer’s API to integrate secure, custodial wallets into your platform — no key management required.

> [xaferapi.apacx.io](https://xaferapi.apacx.io/)

### Custodial Integration Model

Xafer currently provides a Custodial Integration Model, where clients do not need to manage any private key material. Xafer securely handles the entire lifecycle of key generation, sharding, storage, and signing using a robust MPC-based infrastructure.

Clients integrate via simple API calls, enabling them to perform secure wallet operations without running signature nodes or managing cryptographic infrastructure. This model is ideal for Web3 products, SaaS platforms, and startups seeking fast, secure deployments with minimal engineering overhead.

**Key highlights:**

| Mode Type             | Key Ownership               | Risk Control          | Dev Effort            |
| --------------------- | --------------------------- | --------------------- | --------------------- |
| Custodial Integration | Keys fully managed by Xafer | Risk managed by Xafer | Low (API integration) |

### Third-Party Wallet Integration

Xafer can be integrated as a backend security module into existing wallet services, exchanges, or transaction platforms. It’s designed to be UI-agnostic, allowing developers to maintain full control over frontend design and business workflows while outsourcing the cryptographic and risk control layer.

Use cases include:

* Integrate Xafer's WaaS service into the backend to replace local private key management.
* Receive deposit, withdrawal, and risk event notifications from Xafer.

This approach significantly enhances backend security and compliance readiness, with minimal changes to the existing architecture.

### Integration Recommendations

Whether you're running an enterprise backend (ERP, finance), a SaaS product, or a Web3-native app, Xafer recommends modularizing your wallet layer as a standalone service. This decouples critical asset logic from your core application and improves risk isolation and maintainability.

Recommended practices:

* Wrap Xafer APIs/SDK into internal service layers for consistent wallet access
* Embed approval workflows within finance or compliance systems
* Use webhooks to receive real-time alerts on risky operations or transaction events

This architecture scales well as business needs evolve, while maintaining a strong security posture.

### Pre-Integration Checklist (Non-Technical)

Before proceeding with integration, enterprises should clarify the following:

* **Define wallet use case**: Is it for user fund custody, treasury ops, or contract interaction? Different cases may require different flows.
* **Identify system touchpoints**: Can your internal systems (e.g. finance, admin backend, risk tools) receive webhook alerts?
* **Team alignment**: Are the technical, product, finance, and compliance teams aligned on roles, milestones, and deployment timelines?

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apacx.io/xafer-waas/xafer-waas/integration-and-onboarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.