> For the complete documentation index, see [llms.txt](https://apidocs.onekeypayments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.onekeypayments.com/knowledge-base/deposits-with-cards-sdk/with-user-interface.md).
# With User Interface
{% hint style="info" %}
**Requirements:**
* Integrate the OneShot Experience flow within the [Deposit Creation Endpoint](/api-documentation/quickpay/endpoints/deposit-creation-endpoint.md) for credit and debit cards payment methods.
* Install the [Cards SDK](/deposits-tools/cards-sdk.md).
{% endhint %}
### 1. Create a Deposit
It must be a deposit for a **credit or debit card payment method** and within the **OneShot Experience**, therefore all the required payer information should be included in the request. Additionally, merchants opting to use our Cards SDK should send the parameter **`token_requested`** with value **`true`**.
**Example request**
```javascript
{
"invoice_id" : "1000000001",
"amount": "1000",
"country": "MX",
"currency": "MXN",
"payer": {
"id": "11",
"document": "CURP4321TEST",
"first_name": "Ricardo",
"last_name": "Carlos",
"email": "juanCarlos@hotmail.com"
},
"payment_method": "VI",
"client_ip": "123.123.123.123",
"back_url": "https://www.d24.com/deposit_cancelled",
"success_url": "https://www.d24.com/deposit_completed",
"error_url": "https://www.d24.com/deposit_error",
"notification_url": "https://www.d24.com/d24/notify",
"token_requested":true
}
```
**Example response**
```javascript
{
"checkout_type": "ONE_SHOT",
"redirect_url": "https://pay.depositcheckout.com/validate/4BmNaZNydAokLUzAg2jbCrzqBsyyBTVV",
"deposit_id": 981624749,
"user_id": "11",
"merchant_invoice_id": "1000000001",
"payment_info": {
"type": "CREDIT_CARD",
"payment_method": "VI",
"payment_method_name": "Visa",
"amount": 1000.0,
"currency": "MXN",
"expiration_date": "2024-04-11 18:11:11",
"created_at": "2024-04-11 18:01:11"
},
"checkout_token":"4BmNaZNydAokLUzAg2jbCrzqBsyyBTVV"
}
```
The **`checkout_token`** contains the information within the context of the generated deposit. This information will be decrypted and consumed by the SDK in order to adequate the checkout experience.
### 2. Instantiate Cards SDK
Now you need to instantiate the **already installed** Cards SDK. [Here](/deposits-tools/cards-sdk.md) you will find all the technical aspects within instantiation. Remember to retrieve your **publicKey** from the Merchant Panel, and define the proper **environment**.
### 3. Display the Cards SDK component
Now you can display the **CreditCardForm**. In order to do so, you need to send in the **`authToken`** parameter, the value obtained in the **`checkout_token`** of the first step alongside the rest of the parameters (`country`, `onTokenGenerationError` and `onBack`).
The component will take care of the deposit creation by collecting the payer's credit card, and then processing the transaction with the acquirer.
### 4. Retrieve the Deposit final status
Everytime that the deposit changes it's status, you will receive a webhook notification with the `deposit_id` for you to retrieve the Status.
Once the user clicks in the Complete button, we will process the transaction and you will receive such webhook.
---
# 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://apidocs.onekeypayments.com/knowledge-base/deposits-with-cards-sdk/with-user-interface.md?ask=&goal=
```
`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.