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

# Quickstart

> Compares Saber's SDK versus API onramp integration and Saber-pool versus external-wallet custody, listing merchant, key, user, and webhook prerequisites.

Buy crypto with fiat and have it deposited into a wallet of your choice. Saber offers two integration approaches — a web-hosted SDK, or the onramp APIs — and lets you choose whether to keep a pool account with Saber or transfer to an external wallet.

![Flowchart of the onramp quickstart flow: view payment method and beneficiary details, create a buy order, convert fiat to crypto, deposit crypto in the user's account, and wait for a completed callback](https://files.readme.io/ac4f187a22b66e375983d9e54a367d46051ba63efc7690338cdb5f3e1b1362f4-image.png)

### SDK versus API

| **Feature**             | **API Flow**                                                                         | **SDK Flow**                                                                     |
| ----------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------- |
| **Ease of Integration** | Requires custom development with multiple API calls (authentication, KYC, payments). | Quick setup with prebuilt UI and minimal coding effort.                          |
| **Customization**       | Full control over the user interface, branding, and workflows.                       | Limited to predefined UI and flows offered by the SDK.                           |
| **Error Handling**      | API errors must be handled manually (e.g., authentication failures, KYC rejections). | SDK abstracts most errors and only requires handling final transaction statuses. |
| **Implementation Time** | Longer due to custom development and testing.                                        | Faster setup with ready-to-use components.                                       |

### Keeping crypto in Saber or transferring it to an external wallet

| **Aspect**      | **Keeping Crypto in Saber Pool**                          | **Transferring to an External Wallet**                            |
| --------------- | --------------------------------------------------------- | ----------------------------------------------------------------- |
| **Security**    | Safely stored with enterprise-grade encryption.           | Full control but requires secure management of private keys.      |
| **Convenience** | Instant access for transactions within Saber's ecosystem. | Additional steps are required to transfer funds for transactions. |
| **Fees**        | No network fees; standard network fees for withdrawals.   | Network fees apply for all transfers, plus potential wallet fees. |
| **Flexibility** | Limited to Saber-supported cryptocurrencies.              | Can be used across multiple platforms and wallets.                |
| **Control**     | Saber manages private keys and recovery processes.        | The user is fully responsible for private key management.         |

## Prerequisites

1. **Register as a Saber merchant** — reach out to our team if you haven't.
2. **Set up your keys** — see [Configuring Your Keys](/getting-started/auth).
3. **Create a user** — see [Registering Users](/user/registration).
4. **Configure your webhooks** — see [Webhook Configuration](/client/dashboard/webhooks).

## Implementation

* **SDK flow** — contact your Saber representative for SDK integration docs.
* **API flow** — see the [API Quickstart](/docs/quickstart-3).


## Related topics

- [Quickstart](/docs/api-method.md)
- [API Quickstart](/docs/quickstart-3.md)