Automate your P2P order payments by operating the bank app on one or several Android phones, using the Silver5 desktop app and BlueStacks.
The Mobile variant automates your P2P order payments with the Silver5 desktop app, which operates the bank app on an Android phone (the BlueStacks emulator or a real phone over USB). Silver5 sends you the orders and the app pays them on its own, one by one — and you can have several phones paying in parallel.
Video tutorial — From zero to a working automatic payment
That video walks the whole flow in one go. If you’d rather take it one piece at a time, each step has its own short video below, under Step-by-step setup.
Each of your bank accounts lives on one phone. When an order comes in, Silver5 looks at which account the money has to come out of and sends the payment to the phone assigned to that account. The desktop app opens the bank app on that phone and runs the payment step by step, all the way to capturing the receipt.That’s where the three rules of the model come from:
The account decides
Which phone a payment runs on is decided by the bank account, not by the operator. Nothing you touch in the desktop app changes the routing.
One payment per phone
Each phone handles one payment at a time. Payments from the same account run in sequence; different phones run in parallel.
One bank per phone
Two accounts at the same bank need two phones: on the same device they overwrite each other’s session.
If the phone assigned to an account is off or disconnected, that payment does not run on a different one — it waits. That’s by design: a payment run on the wrong phone comes out of the wrong bank account.
BlueStacks → bank app → desktop app → credentials → connect → bank account + phone → test payment → activate
Everything involving the desktop app comes first and together; you touch the cloud only once, at the end.
Activating is always the last step. Once you activate the integration, real payments start coming in — so the test payment goes before it, never the other way around.
Open BlueStacks and create an instance. That instance is going to be your phone.Turn on the debug bridge once: ⚙ Settings → Advanced → Android Debug Bridge → ON. Without it, the desktop app can’t see the phone.
Step 1 — Installing BlueStacks (video in Spanish)
2
Install the bank app and log in once
Inside the instance, open the Play Store and install your bank’s app. Log in once by hand and leave the session open.
Leave the bank app logged in. If the session closes, the payment won’t go through.
3
Install the Silver5 desktop app
In Silver5 → Settings → Desktop app connection → Download. Install it and open it.
Step 2 — Installing the desktop app (video in Spanish)
4
Check that the phone shows up on its own
In the app’s 📱 Devices section, your phone appears on its own. There’s nothing to enter by hand.
Step 3 — Connecting the device (BlueStacks) (video in Spanish)
5
Load the bank credentials
In the Credentials section you’ll already see the fields for the bank you installed, grouped by phone. Enter the username and password and save.
🔒 Credentials are stored encrypted in your computer’s keychain (Keychain on Mac, Credential Locker on Windows). They never travel to Silver5 nor are they stored in plain text. You hold custody.
6
Connect the app to Silver5 (token)
In Silver5 → Settings → Desktop app connection → Generate token. Confirm with your 2FA code. The token is shown only once — copy it right then.In the desktop app, paste the token and tap Connect to Silver5. At the top it should read 🟢 Connected to Silver5.
Step 4 — Connecting the desktop app to Silver5 (video in Spanish)
7
Create the bank account and assign it the phone
In Silver5 → Bank accounts → New. Choose the bank, the Mobile channel, and assign the operator who has the desktop app open.On the Device card, tap Search and pick the phone. That’s where this account’s money will come out of.
Step 5 — Creating the bank account (video in Spanish)
8
Run a test payment
Before activating anything, run a test payment: pick the account, a small amount, and a destination of your own.Watch the emulator while it runs — that’s exactly what it will do with every order.
9
Create the integration and set the limits
If the test payment went through, go to the bank account and create the integration. Choose which payment method it’s for and set the limits.
Step 6 — Creating the payment agent (video in Spanish)
10
Activate
Activate the integration. From that moment on, orders are paid automatically, within the limits you set.
Leave the desktop app open and the phone on. That’s all.
You can have several bank accounts paying in parallel, one per phone. To add a phone, you only repeat the emulator part:
Video tutorial — Adding more than one device (video in Spanish)
1
Create a second BlueStacks instance
Same as the first one, with its Android Debug Bridge → ON.
2
Install the other account's bank and log in once
Leave the session open, just like on the first one.
3
Load that phone's credentials
In Credentials you’ll now see two groups, one per phone: each asks for the credentials of the bank installed on it. Enter the second one’s and save.
4
Create the second bank account and assign it the second phone
Same flow as before: Bank accounts → New → Device card → Search → the second phone.
5
Create its integration, set limits, and activate
And that’s it: both phones pay at the same time.
One bank per phone. If you have two accounts at the same bank, you need two phones — and both must have their phone assigned. If one is left without a phone, both fall into the same lane and the payment runs on whichever device is available: which account the money comes out of becomes a coin flip.
Once you have more than one phone, a selector appears at the top of the app to choose which one you’re working with. That selector is working context: it changes what you see in the manual views (Payments, Test payment, New bank, Credentials) and does not change which phone an automatic payment runs on. That’s always decided by the bank account.
Each phone handles one payment at a time. Two phones, twice the payments in parallel.
How many phones you can keep running at once depends on your computer’s RAM and cores — with 16 GB and 4 cores it’s 3. The full table, the settings for each instance, and how to verify it on your machine are in PC Requirements.
For banks that require a second factor with a 6-digit code (TOTP), the app can generate that code on its own. You set it up by importing the QR exported from Google Authenticator.
1
Export the 2FA from Google Authenticator
Open Google Authenticator → menu → Transfer accounts → Export accounts. Select the bank account and generate the QR code.
2
Add the QR in the Silver5 app
In the credentials section, add the 2FA using the exported QR code.
🔒 The 2FA secret is stored encrypted on your computer, just like the bank credential. It never travels to Silver5.
When an order comes in, the app loads and validates the data against the order, shows a preview, and runs the payment on that account’s phone.
Manual confirmation
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.
Stop an automation
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.
Silver5 queues the orders and dispatches them per phone: each device runs one at a time, in the order they came in, and different phones move forward in parallel. You don’t have to do anything: leave the app connected and the phones logged in.
Check that Android Debug Bridge is ON in BlueStacks (⚙ Settings → Advanced), or USB debugging if it’s a real phone. Then reopen the desktop app.
A payment is waiting and says the device is disconnected
The phone assigned to that account isn’t online. Payments do not run on a different phone: turn that device on and the payment continues on its own. It’s the safeguard that keeps the money from coming out of the wrong account.
I have two accounts at the same bank and one doesn't pay
Both accounts need their own assigned phone, each with the bank app installed and its own credentials loaded. Check that neither one was left without a device.
I changed the phone selector and the payment ran on the other one
That’s the expected behavior. The selector only changes what you see in the manual views; automatic payment routing is decided by the bank account.
'Silver5 disconnected' in a loop
Don’t open the app twice: only a single instance should run. Close the others and reopen just one.
The bank rejects by location
Use manual confirmation or connect from a connection in the bank’s country.
The payment stopped at 'Confirm'
Check the phone: if it asks for a code or password, complete it (or use manual confirmation).
The bank credentials and the Silver5 token live encrypted on your computer; they don’t leave it. Silver5 never receives your bank username or password.
Credentials are stored per phone: each device uses its own.
A payment only runs on the phone assigned to that bank account. When in doubt, it doesn’t pay.
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.
