Evidence pack
One printable record per payment, with its receipts and their fingerprints, its deposits and who did what and when, to save as a PDF.
Every payment has an evidence pack: one page that gathers everything that proves how it was paid. Open it from the payment's page in the dashboard (Evidence pack), print it or save it as a PDF, and show it to the customer, your accountant or anyone who asks.
What it contains
| Part | What you see |
|---|---|
| Header | Your business, the payment's id, reference, amount and status, and when and by whom the pack was generated. |
| Customer | The name, mobile number and email the payment holds. |
| Destination | The card or account the money was sent to: its bank, its label and the last four digits of the card and the IBAN. Never the full number. |
| Payment | The amounts asked for, received and remaining, the payment methods, every time the customer said they paid (how, with which card digits or tracking number), any review and its outcome, and any overpayment and how it was resolved. |
| Receipts | Every receipt the customer or your team sent, with its status, what the customer typed, the decision, its reason and amount, and each file with its name, size, type and SHA-256 fingerprint. |
| Deposits | Every deposit that was ever on the payment, including a receipt deposit a bank SMS later replaced, with the fields read from the bank SMS when there was one. |
| Timeline | One history, oldest first: the payment's stages, each receipt's history, and every correction from your audit log, each with who and when. |
Dates and times are shown in the Jalali calendar, on Tehran time. Your teammates appear by name; Bezanbecard staff, when they acted, appear as a Bezanbecard operator.
Who can open it
Every member of your team who can read payments can open the pack. Two parts depend on the role:
- Receipt files open from the pack. Each time you open a file a fresh link is made; the images shown on the page itself expire after 10 minutes, so open the pack again before a late print.
- The bank SMS text itself is shown only to owners, admins and support members. Everyone else sees the fields read from it (the bank, the amount, the card or account digits and the trace number), never the message.
Bezanbecard operators who look at a payment for support never get the receipt files or the SMS text.
Each opening is recorded in your audit log. If that record cannot be written, the pack is not shown at all; try again in a moment.
Saving it as a PDF
The pack is a page laid out for printing. Open it, let it finish loading, then use your browser's print command and choose Save as PDF as the printer. Nothing needs installing.
Proving a receipt was not altered
A receipt file is kept exactly as the customer uploaded it: never resized, compressed or converted. When it arrives, Bezanbecard computes its SHA-256 fingerprint, a 64-character code that changes completely if even one byte of the file changes. The pack prints the fingerprint beside each file, and the API returns it as files[].sha256 on the receipt.
To show that a file you hold is the receipt the customer sent, compute its fingerprint and compare it with the pack:
shasum -a 256 receipt.jpgThe same fingerprint means the same bytes. The same fingerprints also power the duplicate warning: a receipt file reused for a second order is flagged to your reviewer.