Pelican withdrawal records: issuer, amount and date
2026-11-17
What this check can establish
A Pelican withdrawal record should be checked as a set of separate fields, not treated as one complete payment result. Compare the issuer name, requested amount, currency, request date, ledger date, reference and any received-credit entry. The available documents support a structured comparison, but they do not establish Pelican’s authenticated operator, payment provider, local permission, account activity or an actual withdrawal outcome.
This guide helps you identify differences between an illustrative request record and another financial record. It does not confirm that either record belongs to Pelican, that a payment was made, or that a particular recipient is genuine. Keep the check limited to information you can independently preserve.
Bank of Zambia requirements
Checked 17 November 2026: application form described for a proposed payment system. Source
Bank of Zambia complaint form
Checked 17 November 2026: form labels Reference and Complaint Description. Source
FATF digital identity guidance
Checked 17 November 2026: guidance discusses digital identity suitability for customer due diligence. Source
Separate the seven key fields
Start by copying each field exactly as shown. Do not replace a displayed date with the date on which you noticed the record. A request date records when a request was entered or made, if the document defines it that way. A ledger date may refer to a separate accounting entry. Neither date alone proves that funds were received.
| Field | What to copy | What to compare | What it cannot prove |
|---|---|---|---|
| Issuer | Name shown on the record | Whether the same issuer appears elsewhere | That the issuer is authorised or connected to Pelican |
| Amount | Number and decimal places | Whether the figures match | That the amount was approved or paid |
| Currency | Currency code or symbol | Whether both records use the same currency | That conversion was applied correctly |
| Request date | Date attached to the request | Whether it differs from a ledger date | That the request was fulfilled |
| Ledger date | Date attached to an accounting entry | Whether it follows or precedes the request | That the entry represents a received credit |
| Reference | Full reference as displayed | Whether it is reproduced consistently | That the reference belongs to a completed transfer |
| Credit entry | Recipient-side amount and date, if present | Whether it matches the request | That a screenshot or statement is authentic |
Use a blank or “not shown” entry when a field is absent. Do not infer a currency from a symbol if the record does not identify it clearly. Do not treat a filename, message timestamp or screen-capture date as the transaction date.
Issuer: identify the document source, not the brand
The issuer field should be copied from the document itself. It may identify a bank, payment institution, account provider, statement generator or another named source, but the available evidence does not establish any particular issuer for Pelican. A logo, colour scheme, email address or document layout is not enough to authenticate a provider.
Record the exact spelling, punctuation and any visible identifier. If two records use different issuer names, preserve both names rather than choosing the one that appears more familiar. If one document has no issuer, mark that field as missing. If the issuer is described only in surrounding text, keep the wording separate from the formal issuer field.
A document can contain several names with different roles. For example, one name may identify a service, another may identify an account holder, and another may identify a processor. Do not merge them into one “issuer” entry. A reliable comparison should show which name appears beside which label.
| Issuer check | Record A | Record B | Difference to note |
|---|---|---|---|
| Formal issuer label | Not supplied | Not supplied | Copy the label exactly if visible |
| Name beside issuer | Not supplied | Not supplied | Do not equate it with the brand automatically |
| Provider or processor wording | Not supplied | Not supplied | Keep separate from the issuer name |
| Identifier or reference | Not supplied | Not supplied | Preserve only what the record displays |
This table is a private worksheet, not a finding about Pelican. It should remain empty where the underlying records do not provide a field.
Amount and currency: compare like with like
Write the amount with all displayed digits. Include a decimal separator exactly as shown before creating a normalised comparison. A difference may arise because two records show different stages, currencies, fees or rounding, but the available evidence does not establish which explanation applies to any Pelican record.
First compare currency. Then compare the numerical amount. Only after those two fields are separate should you calculate a difference. If no currency is visible, write “currency not shown” rather than assigning Zambian kwacha or another currency. A currency symbol alone may not provide enough information for a dependable comparison.
Avoid describing a posted amount as a received amount unless a recipient-side record actually labels it as a credit. A request screen, an internal balance, a payment instruction and a bank statement are different record types. Preserve that distinction in your notes.
| Amount comparison | Request record | Other record | Result to record |
|---|---|---|---|
| Displayed amount | Not supplied | Not supplied | Copy digits and decimals |
| Currency | Not supplied | Not supplied | Copy code or symbol only if shown |
| Fees or deductions | Not supplied | Not supplied | Do not invent or assume a charge |
| Difference | Not calculated | Not calculated | Calculate only after currency is known |
| Label for outcome | Not supplied | Not supplied | Use the document’s own wording |
If the figures differ, write a neutral note such as “amounts differ; reason not established”. Do not turn the difference into a claim that money was withheld, misdirected or received.
Request date, ledger date and credit date
Dates answer different questions only when the record assigns them different labels. A request date may identify when a withdrawal request was entered. A ledger date may identify when an accounting entry was recorded. A credit date may identify when a recipient-side statement shows an incoming amount. The supplied material does not provide dates for a Pelican withdrawal, so those fields must be taken from the records being reviewed.
Keep the original date format and time zone where shown. If one record displays only a date and another displays a date and time, do not add precision to the first record. If the time zone is absent, note that it is absent. A check date of 17 November 2026 is the date on which the available sources were reviewed; it is not a Pelican transaction date.
| Date field | Question for the record | Safe note when absent |
|---|---|---|
| Request date | When does the record say the request was made? | Request date not shown |
| Ledger date | When does the accounting entry appear? | Ledger date not shown |
| Credit date | When does a recipient-side credit appear? | Credit date not shown |
| Check date | When was the source or record reviewed? | Review date not supplied |
A later date does not by itself show that a transfer completed. A matching date does not by itself authenticate either document. Compare the labels, source type and reference together.
Build a neutral comparison record
Use one row per document or statement. Do not overwrite the first version when a later copy differs. Save the original separately from a working copy, and hide unnecessary identity or account details in the working copy. Keep enough context to show the relevant label, amount, currency, date and reference.
The following worksheet separates observation from interpretation. “Not established” is preferable to a conclusion that the records prove a payment or a failed payment.
| Record | Issuer | Amount and currency | Request date | Ledger or credit date | Reference | Neutral observation |
|---|---|---|---|---|---|---|
| Request record | Not supplied | Not supplied | Not supplied | Not supplied | Not supplied | Source and outcome not established |
| Ledger record | Not supplied | Not supplied | Not supplied | Not supplied | Not supplied | Entry meaning not established |
| Recipient-side record | Not supplied | Not supplied | Not supplied | Not supplied | Not supplied | Received credit not established |
When filling the worksheet, use “not shown” for a missing field and “different” only when two visible values can be compared. Keep a separate note for the record type. A statement, request screen, email, receipt and ledger export should not be treated as interchangeable.
Handle references and descriptions carefully
A reference can help distinguish one record from another, but its presence does not prove that the underlying transaction completed. Copy the complete visible reference, including letters, numbers, spaces or punctuation. If two records contain different references, list both. If a reference is partially hidden, record that it is incomplete rather than reconstructing it.
A description field may contain useful context, but free-text wording is not the same as an issuer, date or settlement entry. Keep the description in its own column. Do not treat a user-entered description as an independent confirmation.
The Bank of Zambia complaint form publicly displays separate labels for a reference and a complaint description. That observation describes the form fields only; it does not establish a required reference format, eligibility, transaction or outcome for a particular complaint.
Identity and document checks
The available FATF material discusses the suitability of digital identity for customer due diligence. It does not identify a provider, prescribe documents for Pelican, confirm an operational procedure or establish an identification result. Do not use that general discussion to fill a missing issuer, account holder or payment field.
If a record requests identity or financial information, keep secure originals separate from working copies and remove unnecessary personal details from copies used for comparison. Do not send identity or bank records to an unverified recipient merely because a document requests them. The available evidence does not verify any Pelican contact, account, payment channel or recipient.
A document review cannot authenticate a sender from appearance alone. Check whether the record contains a clear issuer, a coherent reference and consistently labelled fields, but describe gaps as gaps. Do not describe the document as genuine, fraudulent, official or unauthorised without evidence that supports that precise conclusion.
What the evidence does and does not show
The supplied documents support only limited institutional observations and a structured record-comparison method. They do not establish Pelican’s authenticated host, operator, licence, Zambian permission, payment provider, processor, withdrawal amount, account activity, app, contact or received payment. They also do not establish an individual complaint outcome.
For a separate discussion of identity and host scope, use the Pelican host and document scope guide. For complaint-record organisation, see the Pelican complaint sender and proof guide. General background on payment checks is available through the payment checks guide. These links do not confirm a Pelican payment or recipient.
The practical conclusion is narrow: compare issuer, amount, currency, reference and each date as separate fields. If the records do not show the same fields or cannot be tied to an authenticated source, leave the comparison open. A missing field is not proof of a failed withdrawal, and a matching field is not proof of receipt.
Frequently asked questions
Which date belongs to the request?
Use the date attached to the record’s request label. If no request label appears, record that the request date is not shown rather than choosing a message, file or review date.
Who supplied the statement?
Copy the issuer or supplier name exactly as displayed. Do not treat a brand name, logo or email address as an authenticated issuer when the record does not establish that connection.
Where are the currency and reference?
Look beside the amount and in the labelled reference field. If either is absent, write “not shown”; do not infer currency or reconstruct a partially hidden reference.
How should differences be noted?
List both displayed values, identify the field that differs and write that the reason is not established. Keep request, ledger and credit records as separate record types.
What would show a received credit?
A recipient-side record would need to label an incoming credit and show its amount, currency and relevant date. The available evidence does not provide such a Pelican result.
Does a matching amount prove payment?
No. A matching amount is only one comparison point. Issuer, currency, reference, record type and a labelled credit entry would still need separate review.