> ## Documentation Index
> Fetch the complete documentation index at: https://docs.silver5ai.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Mobile Automatic Payments for Binance P2P
> Set up Silver5 AI's automatic payments from the mobile app to verify and execute payments for your P2P orders from anywhere.
The **Mobile** variant automates your P2P order payments with the **Silver5 desktop app**, which operates the bank app on an **Android phone** (a real one over USB or the **BlueStacks** emulator). Silver5 sends you the orders and the app executes them one by one.
Would you rather have payments run in the cloud, with nothing to install and no phone to use? Check out the [Browser Automatic Payments](/modules/automatic-payments/browser) variant.
## How it works
Silver5 sends you the orders and the app pays them on its own, operating the bank app on your phone. To get started you do three things: **generate a token**, **connect the desktop app**, and **connect the phone**. After that, each order is paid automatically — and you can always stop it or confirm the last step by hand.
## What you need
* The Silver5 **desktop app** installed (Mac or Windows).
* An **Android phone** (a real one over USB or the **BlueStacks** emulator) with the bank app installed and **logged in**.
* Your Silver5 **connection token**.
## Downloads
Installers for the Silver5 desktop app and the BlueStacks emulator:
Windows installer (`.exe`).
macOS app (`.zip`) — unzip and open `silver-recon.app`.
Android emulator for Windows.
BlueStacks Air for Mac (Apple Silicon M1–M4).
## 1. Connect the app to Silver5 (token)
Go to Silver5 → **Settings → Desktop app connection** → **Generate token**. Confirm with your **2FA code**. The token is shown **only once** — copy it right then.
In the app, go to the **🔌 Silver5** section, paste the token, and check **Remember token** so you don't have to enter it again.
Tap **Connect to Silver5**. At the top it should read **🟢 Connected to Silver5**.
The connection is **independent of your bank accounts**: you can generate the token and connect before having any banks set up. To change the token, use **🗑 Delete token** and paste a new one. If you want to cut off access, you can **revoke** the token from Silver5.
## 2. Connect the device (phone)
In the app's **📱 Device** section you have two ways to connect the phone.
Plug the phone into the computer with the cable.
On the phone: **Settings → About phone** and tap **Build number** 7 times until it says "You are now a developer". The **Developer options** menu will then appear in Settings.
On the phone: **Settings → Developer options → USB debugging**.
Accept the **"Allow USB debugging?"** prompt that appears on the phone.
In the app, tap **Reconnect device**. It should read **Connected**.
Open BlueStacks → ⚙ **Settings → Advanced → Android Debug Bridge → ON**.
In the app, tap **Reconnect device**. It should read **Connected**.
Keep the **bank app open and logged in** on the phone or the emulator. Without an active session, the app can't carry out the payment.
## 3. Set up a banking integration
In Silver5 → **Banking integrations → New**.
Select the **bank** and the execution **rail**:
* **Pago Móvil** — phone + ID number + destination bank.
* **Interbank** — 20-digit account + ID number + destination bank.
Link the integration to your Binance **ads**.
You don't need to have the integration set up to connect the app: you can add it later and it syncs on its own.
## 4. Load the bank credential
In the payment section, load the bank credential **just once** (for example, the Lemon PIN, the BanescOnline password, or the Bancamiga username/password, depending on the bank) and check **Remember (keychain)**.
🔒 The credential is stored **encrypted in your computer's keychain** (Keychain on Mac, Credential Locker on Windows). It **never** travels to Silver5 nor is it stored in plain text. You hold custody.
## 5. Set up two-factor authentication (2FA)
For banks that require a second factor (2FA) with a 6-digit code (TOTP), the app can generate that code on its own. To set it up, import the 2FA by exporting the QR code from Google Authenticator.
Open Google Authenticator → menu → **Transfer accounts → Export accounts**. Select the bank account and generate the **QR code**.
In the payment section, add the 2FA using the **exported QR code**. {/* CONFIRM: exact location/control in the app */}
🔒 The 2FA secret is stored **encrypted on your computer**, just like the bank credential. It **never** travels to Silver5.
## 6. Execute a payment
When an order comes in, the app **loads and validates** the data against the order and shows a preview. Then it waits for you to confirm the payment manually.
Enable **Manual confirmation** when the bank doesn't allow confirming from outside. The app prepares and validates everything, then stops right before the last step. You (or the customer) do the last step —**Confirm** and your password— **on the phone**; then you go back to the app, tap **I've confirmed**, and the app captures the receipt.
The **⏹ Stop** button cuts off the automation at any time, before sending. The app stops cleanly between steps, without leaving the payment half done.
The app **blocks the send** if the data (ID number, phone, bank, or amount) doesn't match the order.
## 7. Multiple orders in a row
Silver5 queues the orders and passes them to the app **one by one**. Payments to the **same account** are made in order (one finishes, the next starts); different accounts can run in parallel. You don't have to do anything: leave the app connected and the phone logged in.
## 8. Common issues
Check the USB / Debugging connection or the BlueStacks ADB (step 2) and tap **Reconnect device**.
Don't open the app **twice**: only a single instance should run. Close the others and reopen just one.
Use **manual confirmation** or connect from a connection in the bank's country.
Check the phone: if it asks for a code or password, complete it (or use manual confirmation).
## Security
* The **bank credentials** and the **Silver5 token** live **encrypted on your computer**; they don't leave it.
* The **last step of the payment** can always be done or confirmed by you.
* The app **does not confirm** a payment whose data doesn't match the order.
The video tutorials are pending upload. Replace each `PLACEHOLDER_...` with the real URL of the corresponding video once they're published.