Pre-launchCompliance Ledger data is illustrative · launching when first operator signs
For UKGC-licensed operators

A referral channel your compliance team will actually finish reading.

Closed peer-to-peer. Audit-ready. Built around LCCP SR 1.1.2 before we built the marketing site.

See how it maps
The pitch · in three parts

Why your compliance team will agree.

01 / Risk

Lower SR 1.1.2 exposure than any open affiliate.

No public marketplace, no bonus-listicle SEO, no third-party retargeting. Every message routed through LATE is single-product, carries significant terms inline, and is logged before it lands.

02 / Reach

A UK cohort you cannot reach on Oddschecker.

Friend-of-friend referrals, weighted by recency of in-person contact. Your acquisition CPI sits below typical paid social, with attribution clean enough for your finance team.

03 / Speed

Two-week integration. One contract.

Postback API, S2S deposit handover, named compliance contact, live read-only feed into your monitoring stack.

The controls map

LCCP clauses. Mapped to features.

LCCP SR 1.1.2

Responsibility for third-party marketing

The Compliance Ledger gives you a live read-only feed of every offer LATE has sent on your behalf. Anonymised at the user level, named at the operator level, exportable as a single audit artefact.

See the live feed →
LCCP SR 3.5.3

Markers of harm

Three offers per sender per recipient per seven days. Auto-cooldown if a user taps and abandons more than twice. Direct integration with your existing deposit-limit and self-exclusion APIs.

See the rate-limit policy →
LCCP SR 5.1.12

Misleading marketing

Every offer card renders product type, value, and significant terms in the same size as the headline. No drip pricing. No fine print. Server-stamped at send-time so the affiliate cannot edit them.

See the offer-card design →
CAP §16.3.12

No strong appeal to under-18s

Username content filter blocks operator names, gambling terms, and known under-18 cultural cues. No imagery of people. No youth-culture register. Pre-cleared template library, refreshed quarterly with ASA guidance.

See the template approach →
DMCC Act 2024

Affiliate disclosure

The “LATE earns a fee on this referral” disclosure sits at the top of every offer card, in body type, not the footer. Repeated in the redirect interstitial. Echoed on the recipient’s first-run onboarding.

See the disclosure UX →
PECR Reg 22

Granular consent, opt-out default

Per-operator, per-channel consent toggled by the recipient before any push arrives. Withdrawable in one tap from the home screen. Audit-logged. Recorded in the consent ledger you’ll receive nightly.

See the consent UX →
Integration

Postback in, credit out. Two endpoints.

Plain-English spec
Sandbox on request

When a referral becomes a registered, depositing customer at your platform, your server pings ours with a postback. We log it against the originating sender, credit them within our 14-day validation window, and pay out via Stripe Connect.

We mirror the postback fields most UK operators already send to Income Access or Raketech. Two new fields cover the compliance metadata we audit-log — age-verification status and the LCCP SR 3.5.3 risk flag if your monitoring stack flagged the customer.

Full technical spec, sandbox keys, and sample payloads available on request to compliance@lateaffiliates.com. We respond within one working day.

From you to us — when a referral converts
operator IDconversion type (signup · first deposit)value in GBPtimestampcustomer ID hashage-verified flagrisk flag (if any)
From us to you — when an offer is sent
sender hashoffer template IDtimestampaudit log reference
Request the full spec →

Talk to the people who sign the Restraint Report.

One email address. A named compliance contact from day one. We respond within one working day.

compliance@lateaffiliates.com