Zambia evidence desk · Adults 18+ · Information, not legal advice

Pokobet Zambia withdrawal: compare the request and credit entry

2026-11-19

A Pokobet withdrawal request and a separate credit entry should be compared as two distinct records. Match the exact spelling, reference, currency and dates before treating them as connected. The documents available for this check do not authenticate a Pokobet operator, a Zambian permission, an accepted payment route, an account, a withdrawal, a credit entry or an outcome.

That means a request record is not itself proof that money was posted, and a credit entry is not itself proof that it came from the named brand. Keep the original records private, work from copies with unnecessary identifying details hidden, and do not send identity or bank records to an unverified recipient.

What the available documents establish

Only three narrow observations are admitted. Each is kept with the source that supports it. None connects Pokobet to a payment institution, identity process, complaint outcome or credit entry.

Bank of Zambia overview — checked 19 November 2026

Designated payment system institutions

The Bank of Zambia publishes a page on designated payment system institutions.

FATF guidance — checked 19 November 2026

Digital identity guidance

FATF guidance discusses digital identity for customer due diligence.

CCPC form — checked 19 November 2026

Complaint form

The CCPC complaint form includes a field for a complaint title.

Separate the two records first

Give each record its own row. Do not combine a request screen, message, statement line or notification into one narrative before checking the fields. A useful first pass asks what the document actually records, who appears to have produced it, and whether its identifying value is complete.

RecordWhat to copyWhat it cannot prove alone
Withdrawal requestDisplayed reference, spelling, amount and request dateThat a payment was accepted or posted
Credit entryPosting date, currency, amount and transaction descriptionThat the entry came from Pokobet
Identity noticeExact wording, date and stated purposeThat the recipient is verified

Use the record’s own wording. A description such as “pending”, “submitted”, “processed” or “credited” should not be silently treated as another status. If a field is missing, mark it as missing rather than filling it from a different document.

Compare the spelling and reference

Start with the exact name shown on each record. Compare capitalisation only after comparing the underlying letters, spaces, punctuation and any registration or transaction number that is actually displayed. Do not assume that a shortened label, a payment descriptor and a brand name identify the same party.

FieldRequest recordCredit recordResult
Name or descriptorCopy exactlyCopy exactlyExact, different or absent
ReferenceCopy every characterCopy every characterSame, different or absent
Registration or account numberRecord only if shownRecord only if shownMatches, differs or unavailable

A matching word is not enough when the reference, issuer or registration number differs. Conversely, different descriptions may still need a documented explanation before any connection can be considered. The supplied records contain no authenticated Pokobet company mapping, host mapping or payment-party mapping, so those fields remain open.

Check currency and amount without guessing

Write the currency beside every amount. Do not convert a figure to make two rows appear equal, and do not infer a currency from a symbol alone when the record uses a code or a description. If one record omits currency, mark the comparison incomplete.

ComparisonQuestionSafe worksheet entry
CurrencyIs the same code shown on both records?Same, different or not shown
AmountDo the displayed figures match without conversion?Exact match or difference recorded
ChargesIs a separate charge line actually displayed?Shown, not shown or unclear

An amount difference should be recorded as a difference, not explained as a fee, conversion or adjustment unless a separate record supports that explanation. A credit entry may also contain a description that does not reproduce the request wording. Preserve both descriptions for comparison rather than replacing one with the other.

Keep request, processing and posting dates distinct

Dates can describe different events. A request date may show when an instruction was created. A processing date may describe a later status change. A posting date may refer to the entry appearing in a payment or account record. The available evidence does not provide any Pokobet dates, so no supplied record establishes that one event occurred or that any interval applied.

Record the date label exactly as displayed, including the time zone or time if the record provides it. If a date has no label, write “date shown, event unclear” in the private worksheet. Do not use a later date to prove an earlier request, or an earlier request to prove a later credit.

Date fieldEvent it may describeComparison question
Request dateCreation of the withdrawal instructionIs the instruction reference present?
Status dateA displayed change in the request recordWhat exact status wording accompanies it?
Posting dateAppearance of a separate credit entryDoes the entry carry a matching reference?

When dates differ, the difference is a prompt for another record, not a conclusion. A useful comparison has the date, label, time zone where shown and source record together.

Read an identity notice narrowly

An identity notice should be copied as written, including its stated purpose and any deadline or document reference that is actually present. Do not add an address proof, photo ID, timing or other requirement from general expectations. The supplied FATF source provides guidance context only; it does not set a Pokobet-specific request or prove that a particular recipient is authorised.

Before sharing anything, check who sent the notice, which record it refers to and whether the recipient can be independently identified through an accepted, trusted route. If that connection is not established, keep the material private. Redact unnecessary identity numbers, full account numbers and unrelated personal details in working copies.

  • Copy the notice date and exact wording.
  • Note the stated purpose without broadening it.
  • Match any reference to the withdrawal record.
  • Keep a record of what was not stated.

A request for documents does not establish that a withdrawal exists, that it is payable, or that the sender has authority to receive the documents. Those are separate questions requiring separate evidence.

What could connect a request to a credit?

A stronger connection would require the same exact reference, compatible spelling or descriptor, the same currency and amount without unexplained alteration, and dates that can be described as separate events. Even those matches would show a document relationship, not independently establish the identity or authority of the party behind the records.

Use the following decision grid privately. It is a comparison tool, not a statement that any row exists for Pokobet.

ObservationMeaning for the comparisonNext record to seek
Same reference on both recordsPotential document linkIssuer or account statement supporting the entry
Same amount and currency, different referenceUnresolved; do not mergeDocument explaining the reference relationship
Credit descriptor differs from request nameIdentity remains openIndependent record identifying the descriptor
Only a screenshot is availableLimited context and no independent confirmationOriginal downloadable record, kept securely

A screenshot can preserve visible wording, but it may omit surrounding details. Keep the original file or statement where available, record when it was obtained, and avoid altering the original. Do not publish personal information while trying to demonstrate a match.

Prepare a private comparison worksheet

Use one line per record. The worksheet should make gaps visible rather than encouraging a conclusion. It should not contain more personal information than needed to distinguish the records.

  1. Assign a private label such as “request record” or “credit record”.
  2. Copy the exact name, descriptor and reference.
  3. Record the displayed amount and currency separately.
  4. Record every date with its label and time zone where shown.
  5. Mark each field as matched, different, missing or unclear.
  6. Store the original securely and keep the working copy redacted.

Do not send the worksheet, identity documents or bank records to an unverified recipient merely because a notice requests them. A comparison can be completed locally until the recipient and purpose are independently established.

If you need to prepare a complaint record

Keep the complaint account factual and limited to what the records show. Separate the request, any notice and the credit entry. State which fields match, which differ and which are absent. Do not describe an allegation as an established fact, and do not claim that a form will accept, investigate or resolve a matter when that has not been confirmed.

No form was used for Pokobet and no case result is available. For general preparation, see complaint guidance or the brand-specific page on recording a Pokobet complaint and reply.

If the issue concerns a payment record, keep the payment entry, request reference and relevant correspondence together, while removing unnecessary personal data from any copy shared for review. A complaint record should identify the disputed point without adding an unsupported operator, licence, local permission or payment relationship.

Questions to answer before treating the records as connected

Use these questions to make the next decision proportionate to the evidence. A “not shown” answer is useful because it identifies the missing link.

What identifies a withdrawal request?

Its own displayed reference, wording, amount, currency and request date identify the record. They do not by themselves prove that a payment was posted.

What does an identity notice say?

Only the exact notice can answer that. Copy its wording, stated purpose and date; do not add document types or timing that it does not state.

Who records the credit?

The credit record should be read for its displayed issuer, descriptor and reference. The available evidence does not identify a Pokobet payment party or connect one to a credit entry.

How can dates differ?

A request date, status date and posting date may describe different record events. Record each label separately and do not infer an interval that the records do not show.

Which observation would connect the two?

The strongest document link would be an exact shared reference with compatible spelling, currency and amount, supported by a separate record that explains the posting.

What should I do when a field is missing?

Mark it as missing or unclear, keep the original secure and avoid filling the gap from assumptions, a different document or an unverified request.

Bottom line for this check

The supplied documents support a careful comparison method, not a confirmed Pokobet withdrawal or credit outcome. Compare exact spelling, issuer or descriptor, reference, registration number where shown, currency, amount and labelled dates. Keep the request and credit as separate records until a documented connection exists. No authenticated brand-to-company, brand-to-payment or brand-to-local-permission mapping was supplied, so those questions remain open.

For related checks, use the general payment checks guide. For related navigation, use reviews; it does not change the evidence limits described above.

Compare evidence routes

Ready to compare the recorded checks?

Open the single commercial route only after reading the evidence limits.

Compare evidence routes