EVP
Verify control of an email identity through the provider and browser, then bind that evidence to an explicit XCIM decision.
Provider-backed evidenceEVP + OAuth identity evidence - XCIM consent infrastructure
Identity you can verify. Permission you can prove.
Collect email preferences on your website with explicit XCIM consent. If you send email for a client, check which addresses have permission for that mailing.
EVP-ready - OAuth fallback - signed receipts
IDENTITY + CONSENT FLOWHOW IT WORKS
Identity evidenceEVP or OAuth
✓Consent capturedExplicit XCIM choice
✓Receipt issuedSigned + revocable
✓One explicit decision
independent evidenceBuilt for the whole trust chain
Two signals. One durable record.
EVP and OAuth answer who is present. XCIM answers what they agreed to. Emabled keeps those jobs separate so every permission remains clear, portable, and auditable.
Identity evidence, your way
Meet users where identity already lives.
Use provider-backed EVP when browser support is available. Keep your existing OAuth integration as a dependable path for every other user, without changing the consent contract underneath.
Identity without
the silo.
Verify provider-backed identity with EVP or OAuth while keeping provider tokens out of your receipt layer.
Compare identity paths →Consent that
survives the session.
Hosted XCIM consent turns an explicit choice into signed, revocable, queryable evidence.
Read the trust model →A trust layer for
your stack.
Use an API, SDK, or hosted surface across multiple sites while the XCIM contract stays stable underneath.
Build with Emabled →For developers
Get your first signed receipt.
Register your site, publish its email choices, then use your backend to open the consent screen for a test visitor. The guide covers credentials, the return to your site and how to verify the receipt.
Follow the first receipt guide// From your backend, using your registered values POST https://api.emabled.com/v1/consent-sessions Authorization: Bearer <vendor-token> Idempotency-Key: <unique-key-for-this-request> Content-Type: application/json { "issuance_profile": "oidc_hosted_consent", "requested_recipient": "tester@example.com", "manifest_id": "urn:xcim:manifest:example-v1", "use_published_consent_screen": true, "return_uri": "https://shop.example/xcim/return", "identity_profiles": ["oidc-01"], "exchange_endpoint_id": "oxe_example_registered_endpoint" }
Documentation