Pre-integration checklist

Even though GeraNexus is not in general availability, these are the nine pieces of plumbing you want in place before the spec lands. Each is useful on its own.

1. Accept scoped consent tokens

Your auth layer must accept a signed consent token from an external identity provider (we recommend W3C VC-style). The token carries scope, expiry and budget cap.

2. Intent handler

A single endpoint that receives an intent envelope, runs a feasibility check and either returns a commit quote or a rejection with a reason code.

3. Commit-quote TTL

Your pricing engine must be able to bind a price for a bounded time window. Typical TTLs are 30–120 seconds.

4. Escrow rail

Integrate at least one escrow-capable rail. Stripe works in most geographies; local rails (Idram, M-Pesa, UPI, PIX, iDEAL) are needed for the markets you operate in.

5. Receipt store

Immutable, content-addressed storage for signed receipts. S3 with versioning works. Keep them for at least seven years.

6. Dispute SLA

Publish a dispute-resolution SLA — acknowledgement within N hours, resolution within M days. Bind it into the commit quote.

7. Reviewer pool

Decide whether you use an internal trust-and-safety team, a provider like GeraWitness, or both. Build the routing rules now.

8. Telemetry

Emit events at every state transition — intent received, quote issued, quote accepted, settle, dispute opened, resolved. Send to your existing analytics stack.

9. Refund plumbing

Partial refunds are the rule, not the exception. Make sure your finance team can push partials on the rails you integrate.

Post-integration

Run the reference conformance suite (publishing with v0.1).
Join the certification programme (launches with v1.0).
Publish your dispute SLA publicly on your site.

Ready now? Join the integrator waitlist, read the deep dive and follow the roadmap.