Merchant dashboard
Review account status, transaction activity, processing outcomes, and operational notices from one place.
Central workspaceC2C ZIMBO gives approved merchants a focused workspace to submit transactions, monitor processing status, manage API credentials, and maintain their settlement wallet information.
A clear interface for merchants and administrators, with the essential controls needed to submit, review, and monitor payment activity.
Review account status, transaction activity, processing outcomes, and operational notices from one place.
Central workspaceApproved users can securely submit customer payment details through the configured card-processing interface.
Account controlledCreate and revoke API keys for server-side payment submissions and transaction-status retrieval.
Developer readyMaintain the wallet address and network associated with the merchant’s intended settlement destination.
Wallet recordsAdministrators can manage user access, account states, branding, and the transaction-processing queue.
Operational controlCard brand, last four digits, and expiry metadata can be displayed without exposing full card numbers or security codes.
Privacy consciousThe merchant receives portal credentials and an administrator assigns the appropriate account status.
An active merchant enters the transaction information through the secure payment form.
The submitted payment appears in the administrative queue with its masked card metadata and merchant details.
The merchant can follow the transaction state from submission through processing and final outcome.
The portal is designed to display masked card information and processor references while avoiding storage of full card numbers and CVV data in the application database.
Separate merchant and administrator permissions help restrict operational access.
Transaction submission can be restricted according to each merchant account state.
Administrative review can use card brand and last-four data instead of raw card credentials.
Use portal-generated credentials to authenticate server-side requests. Keep secret keys outside browser code and production repositories.
# Example request structure curl -X POST https://c2c.bank.si/api/v1/payments \ -H "X-API-Key: your_api_key" \ -H "X-API-Secret: your_api_secret" \ -H "Content-Type: application/json" \ -d '{ "amount": 250.00, "currency": "USD", "reference": "ORDER-1042" }'
Only authenticated merchant accounts with an eligible active status can proceed to payment submission. Access remains subject to administrator review and platform rules.
No. The administrative interface should display only masked card metadata such as card brand and last four digits, together with the processor reference and transaction information.
Not by itself. The wallet is stored as a settlement destination record. Actual conversion or payout requires a separately integrated and appropriately approved payout provider.
All merchant login buttons on this website open the secure portal at c2c.bank.si.
Sign in to view your account status, manage API credentials, update your USDT wallet information, and submit eligible payments.