Pelican complaint sender and delivery evidence
2026-11-17
The available documents support a careful evidence check for a Pelican complaint, not a finding about a particular case, operator, payment provider or remedy. Compare the name on a response with the name on any financial attachment, then preserve delivery evidence separately. A case number may identify a record, but it does not by itself prove a remedy, payment or authority.
The public material reviewed here is limited. It supports observations about a published consumer complaint form, wording about matters outside a Bank of Zambia form’s mandate, and an application form for a proposed payment system. It does not establish that a Pelican matter is eligible, accepted, referred, paid or resolved by either institution.
What the available evidence establishes
Begin with the document you actually received. Record its visible sender, date, subject, reference number and delivery route without assuming that those details authenticate the organisation behind it. A response can use a name that differs from the name on a financial attachment. That difference is a comparison point, not proof of wrongdoing or proof that the records belong together.
CCPC source — checked 17 November 2026
A consumer complaint form is published. CCPC complaint form
Bank form — checked 17 November 2026
The published form discusses matters outside its mandate. Bank complaint form
Requirements publication — checked 17 November 2026
The publication describes an application form for a proposed payment system. Requirements publication
Separate sender, issuer and recipient
Make three separate entries before drawing a conclusion. The sender is the address, account or channel shown as delivering the response. The issuer is the person or organisation named on the response itself. The recipient is the person or organisation named on an invoice, payment notice, receipt or other financial attachment. These roles can be different. Do not merge them because a message contains the Pelican name or because a file was delivered with the message.
| Record element | Write down | What it can show | What it cannot prove alone |
|---|---|---|---|
| Sender | Visible delivery address, account or channel | Where the message appears to have come from | That the sender is the issuer or an authorised representative |
| Issuer | Name and role printed in the response | Who the response presents as responsible | That the named party controls the relevant account or funds |
| Recipient | Name on the financial attachment | Who the attachment identifies for the transaction | That the attachment relates to the response or a Pelican service |
| Reference | Case, ticket or transaction number | A label for searching the same record | A decision, repayment or completed remedy |
Use delivery evidence as its own record
Delivery evidence answers a narrow question: what shows that a message or file was sent or received through a particular channel? Preserve the original message, visible timestamp, subject line, attachment name and any system-generated delivery notice. If a portal shows a status, capture the status with its date and keep the original export where available. A screenshot is a copy of what was visible at that time; it is not, by itself, confirmation that the named party accepted the complaint or approved a remedy.
Keep the delivery record beside, but separate from, the content of the response. This prevents a delivery event being mistaken for agreement with the allegations, acceptance of responsibility or confirmation of payment. If the message was forwarded, label the forwarded copy and retain the earlier message if you have it. Do not alter the original file to make names or dates easier to read.
Compare a response with a financial attachment
Read the response and attachment independently. Note exact spelling, trading descriptions, reference numbers, dates, currency symbols and any account or payment identifiers. Then mark which details match and which do not. A matching reference can support a request for clarification, but it does not establish the legal or commercial relationship between the named parties.
| Comparison | Response record | Financial attachment | Follow-up note |
|---|---|---|---|
| Name | Copy the visible issuer name | Copy the visible recipient or payee name | Record exact differences without correcting either name |
| Date | Record sent or issued date | Record document or transaction date | Say whether the dates are the same, different or absent |
| Reference | Copy the case or ticket number | Copy the invoice or transaction reference | Record whether either document cross-refers to the other |
| Amount | Record any stated amount, if shown | Record the amount and currency, if shown | Do not treat a figure as proof of payment or entitlement |
| Channel | Record how the response arrived | Record how the attachment arrived | Note whether the channels are documented separately |
What a case number can and cannot do
A case number is useful for organising records and asking a named sender to identify the corresponding file. It may also help you distinguish two messages that use similar wording. Its meaning depends on the record that created it. Without an authenticated explanation, the number does not establish who opened the case, whether the matter was accepted, whether a review occurred, or whether money was paid.
Write the number exactly as shown, including letters, spaces, hyphens and leading zeroes. Record where it appears: subject line, portal field, letter, attachment or receipt. If two documents use different numbers, keep both. Avoid creating a new combined number in your worksheet because that can obscure which identifier appeared on which document.
Private record worksheet
Use a working copy for analysis and keep the original files unchanged. The worksheet should allow another reader to trace each statement back to a particular document without exposing unnecessary personal or banking information.
| Worksheet field | Entry to make | Privacy treatment |
|---|---|---|
| Document label | Give each file a neutral label and note its file type | Do not place an identity number in the filename |
| Source and date | Record the delivery channel and visible date | Keep the original metadata in the secure copy |
| Named party | Transcribe the issuer and attachment recipient separately | Mask unrelated names in the sharing copy |
| Reference | Record each case, ticket or transaction number separately | Share only the minimum needed for identification |
| Attachment status | Note whether the file was present, missing or unreadable | Do not circulate an unredacted financial file unnecessarily |
| Open question | Write the precise mismatch or missing link | Do not fill gaps with an assumption |
Reading the institutional pages carefully
The CCPC page is evidence that a consumer complaint form is published. That observation does not establish that a Pelican matter can be filed, handled, paid or resolved there. The Bank of Zambia form contains information about what happens when a complaint falls outside its mandate. That general wording does not establish Pelican case eligibility, a referral, a complaint test, a contact route or a response promise.
The Bank of Zambia requirements publication describes an application form for a proposed payment system. Its scope does not establish a current legal conclusion, a register result, a Pelican designation, a particular payment service provider, a processor, a payment result or individual advice. Treat each publication as evidence of what that publication says, not as confirmation of the identity behind an attachment.
Privacy before sharing a complaint record
Keep secure originals separate from working copies. Remove or cover identity numbers, full account details, authentication codes, signatures, unrelated correspondence and other information that is not needed for the specific question. Preserve enough context to show the document’s date, sender, issuer, recipient and reference. Keep a private note of what was removed from the sharing copy.
Do not send identity or bank records to an unverified recipient merely because a message requests them. First identify the exact question that the record must answer and share the minimum necessary material through a channel whose recipient you have independently established. If the evidence is incomplete, record the gap instead of treating a missing document as proof of either side’s position.
Practical decision checklist
- Save the original response and attachment without editing them.
- Record the sender, issuer and attachment recipient as separate fields.
- Write every reference number exactly as displayed.
- Preserve the delivery event separately from the response content.
- Compare names, dates, references and amounts without correcting differences.
- Mark what is shown, what is missing and what remains unverified.
- Redact unnecessary personal and banking information from working copies.
For related checks, see the Pelican host and document scope, the general complaints guide and the site’s methodology. The review catalogue is available for navigation, but it does not change the limits of the records described here.
Frequently asked questions
Who is named in the response?
Record the issuer name exactly as displayed, then compare it separately with the sender and any name on a financial attachment.
What shows delivery?
A visible delivery address, timestamp, subject, portal status or system notice can document the delivery event, but not acceptance of the complaint.
Does a number confirm a remedy?
No. A case or ticket number labels a record; it does not by itself prove a decision, payment or completed remedy.
What should be kept with the financial record?
Keep the original attachment with its filename, visible date, delivery context and separate note of the response reference.
Which details need privacy?
Hide unnecessary identity numbers, full account details, authentication codes, signatures and unrelated personal information in working copies.
Does a published form confirm Pelican eligibility?
No. The available institutional pages do not establish Pelican eligibility, referral, payment, resolution or an individual case outcome.