Payment documents, collected with one link.
The payment provider asks for what it needs, your customer uploads it from their phone, and your team follows every request from a single panel. No more receipts and ID photos lost in chat threads.
- ID card, frontApproved
- Deposit receiptIn review
- Customer ID8814207
- Amount$12,500.00
- DecisionApprove or reject
A document request, closed in four steps
Every request gets two private links with the same address pattern. The screen changes depending on who opens it: customers never see the provider’s view, and providers never see other requests.
- Open a request
Pick the site, the payment provider, the customer and the amount. Two links are created instantly.
- The provider asks
ID, bank receipt, card statement or anything else, written in plain words with instructions.
- The customer uploads
A photo, a PDF or a screen recording of account activity, straight from the phone. If something is unclear, they see why and send it again.
- The decision arrives
The provider approves or rejects, you get a Telegram alert, and you close the request.
Documents stay with you, risks don’t
Every image is redrawn from scratch, every PDF is turned into page images and every video is re-encoded into a clean file. Hidden code, macros and location data are stripped out.
Files sit on the server encrypted with AES-256 and only open inside authorised screens.
Customers can’t reopen what they uploaded, so a forwarded link exposes nothing.
Customer links expire, and documents from closed requests are deleted after the retention period you set.
Each site appears with its own name and colour, and alerts go to separate Telegram groups.
Who uploaded, opened, approved or rejected each document, and when, is kept on every request.
Run it for your own brands
On your domain, with your branding, hosted on your own server. Tell us a little about your setup and we will reach out.