> For the complete documentation index, see [llms.txt](https://docs.rocketfuel.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rocketfuel.inc/developer-guides/api-reference/payins/overview.md).

# Overview

**Rocketfuel PayIns API Overview**

1. #### **Sign Up**

   Merchants begin by signing up with Rocketfuel. They must provide basic business and personal information to create an account.
2. **KYB (Know Your Business)**

   The KYB process verifies a merchant's legal and financial standing. This includes submitting company documentation to ensure compliance with regulatory standards.
3. **Approval**

   After KYB verification, Rocketfuel reviews the submitted documents. Once approved, the merchant receives authorization to use the platform for transactions.
4. **Keys Generation**

   After approval, the merchant generates their public and private keys. These keys are essential for securing API communications and handling transactions securely.
5. **Ready to Use APIs**

   Once set up, merchants gain access to Rocketfuel’s PayIns APIs, allowing them to integrate payment processing into their platform and start accepting transactions seamlessly.

   * **RKFL Widget/Payment Page**
     * **Redirect**: Merchants can redirect customers to a pre-built Rocketfuel payment page. This simplifies the payment process without needing custom development.
     * **RKFL Widget**: A customizable payment widget that can be embedded directly into a merchant’s website, allowing customers to complete transactions seamlessly within the site.
   * **Custom User Interface**\
     For businesses seeking full control over the payment experience, Rocketfuel offers APIs to build a custom interface.

***

For detailed information, refer to each section under PayIns.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rocketfuel.inc/developer-guides/api-reference/payins/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.