# How we verify codes | Kobonak

Source: https://kobonak.com/en/how-we-verify/
License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with a link to the source.

# How we verify codes

Each date on a code card is the date stored on that field.

## Three evidence levels

Each card shows the highest level the offer record supports. **Accepted at checkout** means the checkout test applied the code. It does not mean a price discount was measured. A measured price cut is shown as **Savings verified at checkout**. Measured cashback is shown as **Cashback observed**. **Order completed** or **Cashback received** means the record includes that field. A network’s recorded-order date is not that level. A percent the test did not record is not stated as the code’s benefit. Store pages, guides and calculators use that same benefit sentence.

## How we confirm orders and cashback

If you completed an order or received a cashback payout, call Mudrek LLC on [+971-55-132-2497](https://kobonak.comtel:+971551322497) with the code, the store and the country (see the [contact page](https://kobonak.com/en/contact/)). We add a completed-order or cashback field to a record only after an editor has reviewed the proof. A completed order is that field.
When a record has a basket or a screenshot, the card shows subtotal, discount or cashback, shipping and total. Each figure is taken from the sentence that names it. The screenshot file is shown when its name matches the store, country and code. The store page lists the active offers, and each card carries its label and last-checked time. The method and the savings tests are on the [methodology page](https://kobonak.com/en/accuracy-report/). The dates are on the [change log](https://kobonak.com/en/changelog/).

## Five levels on every code

- Listed
- Accepted at checkout
- Savings verified at checkout
- Order completed
- Cashback received
Each card states the level its record supports. Savings verified at checkout means a price cut written with an amount. Accepted at checkout means the code was applied and a price discount was not measured on that test. Cashback observed is the amount on the checkout screen. Order completed and cashback received appear when that field is on the record. An editor writes a verified purchase on the record only after reviewing proof.

## Monthly audit sample

On the first day of each month a scheduled job picks 10 active codes with a fixed shuffle seeded by the month name. The [audit queue](https://kobonak.com/en/audit-queue/) shows the sample and the selection date. A result is written when a checkout test is added to the record.

## The checkout-tested label

The card does not use the word “checkout-tested” as its badge. The three levels above are the badge. A recorded network order is not a checkout result and it is not “Order/cashback confirmed”.

## Four date fields

- **Last network check.** This comes from the affiliate-dashboard check log: the time an editor confirmed the code was still listed, shown for three days after that check. If there is no check in the last three days, we show the date stored on the offer (checked_at) when that date is on the record. The card uses that stored date.
- **Last checkout test.** The day we typed the code at checkout and wrote down the result. This is what the checkout-tested label requires.
- **Last editorial update.** The day the page text changed, from the page date log. It is a writing date, not a code check.
On a store's own public offer we also show **Official terms checked** when we have read the merchant's help page.

## Minimums, caps, expiry and exclusions

A minimum, cap, end date, or exclusion is shown when the offer record contains it. A link to the merchant’s terms or promo page is added when that URL is already in the data.
“Eligibility tested” is shown as “guest checkout, one basket” when a basket was written on the record. If it was not, that line is omitted. On a tested card the date is labelled Checkout test. In the code-details table, Last checked is the later of that checkout test and a recorded acceptance recheck. Provenance lists those tests before an older network-terms date, and labels the older date First recorded. It is not the latest verification. Next scheduled check is 14 days after that later test.

## Shopper reports

Each code asks “Did this code work?” with Yes and No. When reports are stored for that code and country, the card shows how many and the date of the latest report. A worked percentage is added from 5 reports. At that sample, if No outnumbers Yes, the code is flagged for editorial review. That flag does not change the editorial test label.
Votes are counted per code and country. Two offers that share one code in one country share one sample.
“Did this code work?” is on every code, separate from the editorial test. It sends the code, country, yes or no, and the Gulf date. One report per visitor, per code, per day. The page shows the count and the latest report date when a report is stored, and yes, no and the worked percentage from 5 reports. Comments appear after they are approved in the moderation queue.
A checkout-tested label stays through the test date plus 14 days on the Gulf calendar. Each tested card shows “Next scheduled check” as that date. The fresh or stale decision uses one rule: the calendar day in Asia/Dubai. The label stays fresh through the recheck date. It becomes “Last tested” with an amber “stale, retest due” warning only when that Dubai day is after the recheck date. The same comparison runs in the built page and in the browser. A code tested today is not stale. A stale card is muted, carries an amber “Retest due” badge, and sorts below cards that are not stale. No rebuild is required for that change: the same Dubai comparison runs when the page is served and in the browser. The recorded level stays under that warning. The same date is in the offer’s structured data as “Checkout-tested label valid through”. A code whose checkout test did not apply keeps the label “Not applied in our test” and sits after the active cards. The test date and result stay on the page as its test history. We do not write a test that did not happen.

## Who tests, and how corrections are handled

Every test is performed and signed off under the Kobonak editorial team (Mudrek LLC). Each record carries a test-session ID. A stored screenshot carries the SHA-256 of that file. Content is overseen by editor Rami Hakim. On 4 Nov 2026 the editorial team manually checked the listed codes at checkout. A basket, a benefit, and a screenshot are shown when the record includes them. Namshi FIRST is labelled “App-only offer: not verified on the website.” Victoria’s Secret Z6EZ requires sign-in to apply. Namshi ANP9’s observed benefit is cashback, not a price cut, and the cashback shows on its own line and does not lower the checkout total. The checkout-tested label becomes “Last tested … - stale, retest due” 14 days after the later of the test date and a recorded retest. On 9 November 2026 the site owner retested screenshot-tested codes and recorded that they were accepted again. The card shows that date as “Code rechecked (acceptance only)”. The same day the editorial team recorded guest-cart screenshot tests for DR63 in Saudi Arabia and the UAE, AC37 in Saudi Arabia, and MJ4 in Saudi Arabia and the UAE. Those dates are the tested_at or retested_at fields, and they appear on the [methodology page](https://kobonak.com/en/accuracy-report/) and the [change log](https://kobonak.com/en/changelog/).
If a page disagrees with the offer record, or with a merchant page we have read, we change the page and add a dated entry to the [corrections log](https://kobonak.com/en/corrections/): what was wrong, what changed, and which pages. Entries are not removed. Store pages link here so the rule sits next to the code.
Offer ID, date received and original terms are shown when those fields are on the offer record.

## Daily freshness check

A daily GitHub Actions job rebuilds and deploys the site. It re-reads recorded end dates and the 14-day rule. A code whose end date is before the Dubai day of that build leaves the active lists. A code whose recorded end date is before the Dubai day of that build leaves the active lists. The checkout-tested label stays through the test date plus 14 days. The next Dubai day it becomes “Last tested” with a stale warning. The code stays on the page. The job rebuilds the site from the records. [/status.json](https://kobonak.com/status.json) is written in that build and includes the check date. The footer shows “Last automated freshness check” from the same date.
Offer selection: active partnership codes issued to Kobonak for that store and country. Next to them we show the store’s own public offer or promo page when we have read one, including when it pays no commission.

## How the cards are ordered

The order is the function in the code. The full description, including the groups and the rule that commission is not an input, is on [how we rank codes](https://kobonak.com/en/how-we-rank/). Store pages link to that page.

## Track record

The earliest published date in the page date log is 31 October 2026, the day kobonak.com launched. The repository history begins with the initial import on the same day. The first imported date log also held dates from 30 September to 30 October 2026, before launch; those pages now show 31 October 2026, because no page was public before the launch.

## Structured data checks

Structured data checks: last build 2026-11-18, 608 pages checked. Each page’s JSON-LD offers matched the visible card code, label and dates.

## The rest of the check

- Every partnership code we publish was issued to us by the store's program. Its rate and cap come from that program's terms or from a checkout test.
- We match store facts (fees, delivery, returns, payment) against the store's official pages and show the review date.
- When a term changes or we find a mistake, we correct it and list it on the [corrections log](https://kobonak.com/en/corrections/).
- We review reader reports of codes that do not work.
We don't show fake usage counters, star ratings, or discount figures that no source we can point to has stated. The store makes the final call on any discount at checkout.
