Internal console for operating the MicoPay cash network: find a user or an operation, understand why an agent cannot operate, and compare MicoPay's records with the on-chain escrow.
Status: Architecture and design. There is no application code yet. Network: the MicoPay backend currently runs on Stellar Testnet. Custody: the console has no power over user funds and never acts on behalf of a user or agent.
MicoPay's support and operations staff. It is not a portal for agents or app customers, and it is not a public service.
- Operator access: individual sign-in with two-step verification, directory search, user records, internal notes, and a history of staff actions.
- On-chain state: each operation shows its MicoPay status next to its contract status, with differences flagged.
- Agent readiness: for each agent, MicoPay requirements and Stellar checks, with a clear verdict and the action the agent must take in their own wallet.
The first version is read-only for accounts and funds, apart from internal notes.
Funds stay in user wallets or in the on-chain escrow. The console will have no function to move, freeze, or redirect them. The contract only pays the parties of a trade and its fee, whoever submits the transaction.
- This repository: the web application (planned stack: React, TypeScript, and Vite).
- MicoPay Protocol: the admin API, migrations, and business rules. The console does not create a second user database.
See the ecosystem map.
Read the public plan.
There is nothing to run yet. This section will be completed with the first application code.
- Nothing is implemented or deployed.
- The console depends on API work in MicoPay Protocol that does not exist yet.
Do not disclose vulnerabilities in public issues. Report them privately to eric@micopay.com.mx.
This repository is a design document, not a financial service, an investment product, or a promise of availability.