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

Slotobit withdrawal records: what to compare

2026-11-18

If you are comparing a Slotobit withdrawal request with a separate credit entry, treat them as two records until their identifying details connect. Compare the reference, currency, amount, date and wording in each record, but do not treat a matching item as proof of a completed payment without a reliable supporting record. The supplied documents do not establish a Slotobit payment channel, provider, account result, local permission or completed withdrawal. They support a careful comparison process rather than a payment outcome.

What this check can establish

A document comparison can show whether two records use the same reference, describe the same currency, contain corresponding amounts, or place events in a consistent sequence. It cannot, by itself, establish who operated a service, who controlled a payment account, whether an identity request was valid, or whether money reached a particular account. Keep those questions separate so that an incomplete match is not presented as a confirmed result.

Begin with the exact records already in your possession. Preserve the original file or message in a secure location. Make a working copy for notes, remove unnecessary personal identifiers from that copy, and record when the copy was made. Do not replace an original with a screenshot, cropped image or rewritten transcription. If a record is only visible in an account area, note that it was viewed without claiming that the account, sender or payment was independently confirmed.

Bank of Zambia report — checked 18 November 2026

2024 national payment systems report is published.

Separate a request from a credit entry

A withdrawal request is a request-side record. It may describe what was asked for, when the request was made, and an identifier assigned to that request. A credit entry is a receiving-side record. It may describe an entry posted to an account or statement. The two records can have different labels and dates. Neither label should be changed to make the records appear more connected than the documents show.

RecordQuestions to askWhat not to infer
Withdrawal requestWhat reference, amount, currency and request date are shown?That a request was approved or paid.
Credit entryWhat reference, amount, currency and posting date are shown?That the entry came from Slotobit.
Supporting messageDoes it identify the same event in clear terms?That a sender or account has been authenticated.

Use the record’s own terminology. “Submitted”, “pending”, “processed”, “credited” and similar wording should not be treated as interchangeable. If the request says one thing and the account record says another, preserve both wordings and mark the difference. A missing reference is also a result of the comparison: record it as missing rather than creating a substitute reference.

Build a reference comparison

References are useful only when their location and meaning are clear. Copy each reference exactly, including letters, numbers, hyphens and any leading zero. Record whether it appears on a request screen, message, statement, receipt or another document. If a credit entry has a different reference, do not assume that one is a payment processor reference or that the other is a platform reference unless the document expressly explains that distinction.

FieldRequest recordCredit recordComparison note
ReferenceCopy exactlyCopy exactlySame, different or absent
CurrencyUse the displayed code or symbolUse the displayed code or symbolMatch or unclear
AmountRecord displayed precisionRecord displayed precisionSame, different or incomplete
DateLabel the event shownLabel the posting event shownSequence only; no conclusion

A reference that matches exactly is a useful observation, but it is not a standalone confirmation of source or settlement. A reference that differs may reflect separate systems, different stages or unrelated records. The safe conclusion is limited to what the records actually share. If the documents use different currencies, preserve the original currency and do not calculate a conversion unless the conversion basis is available and relevant to the comparison.

Read identity wording without overclaiming

An identity notice can ask for information, describe a review, or refer to customer due diligence. Those are descriptions of wording, not proof that a particular person, company or account has been verified. Note the exact request, the date shown, the stated reason and any reference attached to the notice. Avoid treating a general explanation of digital identity as an instruction to submit records to an unverified recipient.

FATF guidance — checked 18 November 2026

Digital ID guidance discusses suitability for customer due diligence.

The cited guidance does not prescribe a Slotobit submission, account check or payment outcome. Therefore, if a notice mentions identity, record it as an identity-related statement and keep it distinct from the payment comparison. Do not infer that an identity request proves a local relationship, a valid operator identity, a completed review or an entitlement to receive funds.

Identity wordingRecord it asDo not turn it into
Request for informationThe notice asks for specified informationProof that the recipient is verified
Review or check mentionedThe document refers to a reviewProof that the review was completed
No identity wordingNo identity statement in that recordProof that no check occurred

Keep any unnecessary identifying information out of working notes. A practical worksheet can use neutral labels such as “Record A” and “Record B”, with only the final four characters of a reference where that is enough for internal comparison. Store the unredacted original separately and avoid sending identity or bank records to a recipient whose identity and purpose have not been independently established.

Compare currencies and amounts

Start with the currency shown on each record. A symbol alone may be unclear, so write the displayed code when one is present. Then compare the numeric amount without silently rounding it. A request may show an amount requested, while a credit entry may show an amount posted. Fees, conversion or a different displayed precision could affect the figures, but those possibilities must not be asserted unless the records explain them.

Use a note such as “same displayed currency and amount” only when both records actually show that. If one record omits currency, mark the currency as absent. If the amounts differ, preserve both values and describe the difference without labelling it as a fee, loss or successful adjustment. The comparison should remain factual even when the reader expects a payment explanation.

Keep document dates separate from posting dates

A date can describe when a request was made, when a message was issued, when a record was created, or when an account entry was posted. Use a separate column for each date label. Do not rewrite a posting date as the date of the request. A later date does not prove that the earlier request caused the later entry, and an earlier-looking date does not prove that an entry was available to the recipient at that time.

Write dates in the format displayed by the record and add a plain-language label. For example, “request date”, “message date” and “posting date” are different fields. If the timezone is not shown, do not add one. If a date is unreadable or incomplete, record the limitation rather than completing it from context.

What the payment-systems source does not show

The Bank of Zambia publication cited here is a historical national payment-systems publication. Its reviewed cover and preamble do not establish a current Slotobit payment channel, a provider, a particular payment, or a connection between a withdrawal request and a credit entry. It is therefore background context, not a transaction record. Keep that distinction visible in your notes and in any explanation given to another person.

A source about payment systems can help a reader understand why payment records may contain different fields, but it cannot fill a missing reference or authenticate a statement. The comparison must still rely on the actual request and credit records. If those records are unavailable, say that the comparison could not be completed.

Use a neutral comparison worksheet

A short worksheet can make the distinction between observation and conclusion clear. Use one row for each record and keep a separate notes column. The worksheet should not become a replacement for the original documents. It is a map of what each document says.

Worksheet itemRecord A: requestRecord B: creditResult
Reference and locationExact text and where foundExact text and where foundMatches, differs or absent
Currency and amountDisplayed currency and figureDisplayed currency and figureSame, different or unclear
Date labelRequest or other stated datePosting or other stated dateOrder only
Identity wordingExact wording or none shownExact wording or none shownSeparate issue
Document limitationMissing field or unclear textMissing field or unclear textOpen question

At the end, write a conclusion with three parts: what matches, what differs, and what remains unknown. A careful conclusion might say that the records share a reference but do not independently establish the source of the credit. Another might say that the request contains an amount and date while the credit record lacks a matching reference, so the connection remains unshown. Keep the conclusion no broader than the worksheet.

Keep complaint information distinct

If the comparison leaves an unresolved question, preserve the records and write down the issue in neutral terms. Identify the document, its date, its reference and the precise discrepancy. Do not describe an allegation as an established event. Do not publish unnecessary identity or bank details. If a person chooses to investigate a complaint route, they should read the recipient’s own current instructions and decide what information is appropriate for that route.

CCPC page — checked 18 November 2026

Public complaint page is published by the Commission.

The reviewed page heading does not establish jurisdiction for a particular dispute, identify a direct recipient for a Slotobit matter, or show how a case would be handled. It also does not establish the outcome of any complaint. Treat it as a public page heading and confirm any current process from the page itself before relying on it.

For a private record, keep the original request, credit record and relevant messages together but separate from the worksheet. Use a clear file name that does not expose unnecessary identity information. Record the check date as the date you reviewed the document, not as a document date. A later review should add a new note rather than overwrite the earlier one.

Practical decision points

  • If the reference, currency, amount and date all align, record that they align; do not call the payment completed solely on that basis.
  • If only the reference aligns, record the partial match and retain the unresolved currency, amount and date questions.
  • If the credit record has no source description, do not assign it to Slotobit from timing alone.
  • If an identity notice appears, record its wording separately from the payment evidence.
  • If a date is missing or unclear, leave it open instead of reconstructing it.
  • If a document asks for sensitive information, avoid sending it to an unverified recipient and keep a secure original.

For related reading, use the payment checks guide, the complaints guide and the Slotobit named documents guide. The review catalogue is available for the wider set of published brand pages; it is not evidence that a payment record has been verified.

Questions readers ask

What identifies a withdrawal request?

Use the exact reference, amount, currency and request date shown on the request record. A request identifier does not prove approval or payment.

What does an identity notice say?

Record the notice’s exact wording, date and reference. It may describe a request or review, but it does not by itself prove that verification was completed.

Who records the credit?

Use the credit record’s own source description. If it does not identify a source, do not assign the entry to Slotobit from timing or amount alone.

How can dates differ?

A request date and a posting date can describe different events. Keep each label and do not present either date as proof that the records are connected.

Which observation would connect the two?

A clear matching reference or explicit record description would be relevant, but it should still be assessed with currency, amount and date details.

What should I keep for a complaint record?

Keep secure originals, a neutral timeline, exact references and a note of each unresolved discrepancy. Remove unnecessary identity and bank details from working copies.

On the available evidence, the responsible answer is limited: a withdrawal request and a separate credit entry should be compared field by field, while their connection remains open unless the records themselves provide a clear link.

Compare evidence routes

Ready to compare the recorded checks?

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

Compare evidence routes