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

Scored complaints in Zambia: a dated evidence check

2026-11-13

For Scored complaints in Zambia, the supplied material supports a limited evidence check rather than a local permission finding. It can help you separate a name printed on a document from the recipient of correspondence and from a financial institution. It does not establish a Zambian licence, local authorisation, a filed complaint, a payment event, a withdrawal outcome or an operator-to-domain match. Treat the status as open evidence, not as a fraud or safety verdict.

What this check can answer

The useful question is not simply whether a brand name appears in a record. The useful question is what that record actually proves, who issued it, which party it names, and whether it relates to the event you are trying to document. A certificate, a complaint form and a technical registration-data explanation have different purposes. Combining them into one conclusion would give each record a wider meaning than the supplied material supports.

Use the source-led method for a broader explanation of how dated records, source roles and limits are kept separate.

Evidence included in the review

Three primary records are available for this bounded check. Each is admitted only for the subject it addresses. The check date is 13 November 2026; that date is not a document date and should not be treated as the date of any underlying event.

Certificate record

Checked 13 November 2026: certificate names Willx N.V.

Complaint-form record

Checked 13 November 2026: Bank form separates matters within and outside its mandate.

Registration-data record

Checked 13 November 2026: ICANN overview describes RDAP as a domain-registration data protocol.

The first record has a foreign scope and does not establish a Zambian licence, local permission, services, another address or a link to a gaming destination. The second record does not show a filing, consent, referral or coverage for Scored. The third is technical and does not independently establish a domain, registrant or operator match. These limits remain in force even if a document appears clear.

Separate the three identities

When reviewing correspondence or a payment concern, write down three separate identities instead of using the word operator for every party. First, record the exact name printed on the relevant document. Second, record the addressee or recipient shown in correspondence. Third, record the financial institution shown on a transaction record, if one is available. A blank field is a valid result; it is better than filling a gap with an assumption.

CheckpointRecord to inspectNeutral entry
Name printed on a documentOriginal document line and surrounding headingTranscribe punctuation and spelling exactly
Recipient of correspondenceHeader, addressee, reply details or delivery recordRecord the named recipient, or mark not shown
Financial institutionStatement, transaction record or payment confirmationRecord the institution as shown, or mark not shown
Event outcomeDated response, decision or status recordRecord only the outcome supported by that record

Do not treat a matching word as a complete identity match. Check spelling, punctuation, date, document type and the role assigned to the name. A name on a certificate answers a narrower question than a name on a payment record. A recipient in an email answers a different question from a party listed in a legal or technical record. If the fields cannot be connected by a dated, reliable record, leave the relationship unresolved.

Use a neutral comparison sheet

A private comparison sheet can prevent a document from being stretched beyond its scope. Make one row for each claim you need to test and state the minimum record that would support it. Do not copy unnecessary identity or banking information into a shared draft. The final wording should describe what is established and what remains open.

Question to testMinimum supporting materialNeutral wording if absent
Does the record identify a named party?Exact document line and issuing contextThe named party is not independently matched
Does it show local authorisation?Relevant local primary permission recordLocal authorisation is not established
Was a complaint filed?Filing receipt, acknowledgement or case referenceA filing is not established
Was money sent or received?Financial record tied to the particular eventA financial event is not established
Was there a response or outcome?Dated response or decision tied to the eventAn outcome is not established

Read the complaint route correctly

The supplied Bank of Zambia form is relevant only to understanding the stated boundaries of that form. It does not show that a Scored complaint was filed, accepted, referred or covered. It also does not collect a reader’s information through this review. If you are assessing whether a matter belongs on an institutional route, read the current form and its stated scope directly, then keep any private submission decision separate from this evidence check.

A complaint record should be tracked in stages: preparation, submission, acknowledgement, request for information, response and closure. Only mark a stage when you have a dated record for it. If there is no acknowledgement, write that no acknowledgement is available rather than treating silence as acceptance or rejection. The complaints guidance provides a general structure for separating those stages.

Build a dated event record

A clear chronology is more useful than a long narrative. Start with the date shown on each record and label the date type. A check date records when a source was reviewed. A document date records when the document says it was created or issued. An event date records when the described conduct or transaction allegedly occurred. These dates should not be substituted for one another.

  • Give each item a short neutral description, such as correspondence received or transaction record reviewed.
  • Identify the source type without assigning a stronger role to it than it has.
  • Record whether the item is an original, a copy or an unverified report.
  • Link an alleged event to a response only when the records share enough detail to make the relationship clear.
  • Mark missing dates, missing recipients and missing financial details as open fields.
StageWhat to recordWhat not to infer
Document reviewCheck date, document date and exact printed nameDo not infer a local permission
CorrespondenceSender, recipient, date and stated subjectDo not infer receipt from a draft
Financial recordInstitution, date, reference and event descriptionDo not infer a recipient from a brand name
Complaint stageSubmission or response record and its dateDo not infer an outcome from silence

Keep originals and working copies separate

Retain an original securely and create a working copy for notes or redaction. The working copy should hide unnecessary identifying data. This separation preserves the ability to check the original without putting full identity or banking details into a draft, message or shared folder.

Working-copy fieldSecure originalRedacted working copy
Personal identification numberRetain privately if presentRemove unnecessary digits
Account or reference numberRetain privately for reconciliationMask the unnecessary portion
Address and contact detailsRetain privately if relevant to the recordHide details not needed for comparison
Payment identifiersRetain privately with the originalMask details not needed to identify the event

Do not send identity documents, bank records or account information to an unverified recipient merely because a message requests them. If a record must be shared for a legitimate purpose, remove data that is not needed for that purpose and keep a note of what was shared. The data-handling guide covers this separation in more detail.

Use domain information as a narrow technical check

Registration-data information can help you understand what a technical lookup is designed to provide. It does not, by itself, prove that a person or company operates a service, that a domain is authorised in Zambia, or that a domain was the recipient of a particular payment or complaint. The supplied material does not establish a domain, registrant or operator match.

If you make a technical comparison, record the exact domain string, the date of the lookup and the field being compared. Keep that result separate from a certificate name, a correspondence recipient and a financial institution. A similar spelling is not enough. A missing field is not evidence that the underlying party does not exist. Avoid describing a technical result as a licence check unless a relevant primary permission record supports that description. The online domain-check guide sets out this narrower comparison.

Browse review evidence

Frequently asked questions

What does the evidence establish about Scored?

The material supports a bounded document check. It does not establish a Zambian licence, local permission, a complaint filing, a payment event, a withdrawal result or an operator-to-domain match.

Does the certificate prove permission to operate in Zambia?

No. The supplied document has a foreign scope, and its presence does not establish permission to offer services in Zambia.

Can the Bank of Zambia form confirm a Scored complaint?

No. The form material does not show that a complaint was filed, accepted, referred or covered for Scored.

What should I compare in correspondence?

Compare the printed name, addressee, date, reference and financial institution separately. Record only what the relevant document actually shows.

What does RDAP add to the check?

It may help frame a technical registration-data check, but the supplied material does not establish a domain, registrant or operator match.

How should I handle copies of personal records?

Keep the original secure, make a redacted working copy, remove unnecessary identifying data, and do not send identity or bank records to an unverified recipient.

Compare evidence routes

Ready to compare the recorded checks?

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

Compare evidence routes