Each customer is a meaningful relationship, configured to your business. The flow below is what every Cardem deployment goes through. No surprises, no theatre, no data hostage situations.
Configuration is the longest phase by design. It's your team setting up your store the way you need it. Provisioning itself takes minutes.
A 30-minute call to understand your markets, currencies, payment providers, compliance posture, and any features beyond standard. We draft a configuration with you on the call. By the end you have an honest read on whether Cardem fits, and we have enough to scope a proposal.
Standard MSA and DPA. Custom-development scope of work for any net-new features. Pricing locked: setup fee, monthly subscription, custom development if any, optional premium support.
We provision your dedicated store: database, storage, secrets, signing keys, custom hostname. Your Super Admin receives a welcome email with first-login credentials and a two-factor setup link.
Provisioning is automated and takes a few minutes. There's nothing for your team to do at this step.
Your Super Admin sets up brand assets, products, pricing, payment providers, content, terms and conditions, shipping methods, and customs templates. We provide documentation and a checklist, and we help where needed.
By the end of week one your store is fully populated on a staging hostname. Your team can place internal test orders against real card, crypto, and bank flows.
Net-new features built into Cardem behind a feature toggle, defaulted on for you. Your custom feature funds the build. Every other customer can opt in over time. This is where the platform compounds.
Custom development runs in parallel with configuration so it doesn't extend your timeline unless the feature is on the critical path. The scope of work spells out which.
Your team tests against the staging hostname end to end: place orders, refund them, run a wholesale credit cycle, generate a customs document, fire the cycle-count flow, hit the audit log, run the data export, run the deletion flow.
Issues are logged in a shared tracker and resolved iteratively. Acceptance testing passes when your team signs off the checklist. We provide a default checklist, and you can extend it.
DNS cutover to your custom hostname. We monitor for 48 hours: error rates, response times, payment success rate, customs queue depth, audit chain integrity. You hand over to your team once the watch window closes clean.
Quarterly check-ins after that. Upgrades coordinated by us with you. Feature requests fed into the Cardem roadmap.
If you choose to leave Cardem, the path off the platform is clean and documented. We'd rather you stay because Cardem fits, not because leaving is painful.
Thirty-day notice on either side. A structured hand-off plan covers when each subsystem freezes, who exports what, and who holds final keys.
A signed-link archive delivered to your Super Admin. Includes a database dump, CSV export of every table, all media files with a manifest, and the full audit log.
Infrastructure decommissioned cleanly. Backups retained for the legal minimum (typically ninety days for tax and customs traceability), then destroyed with cryptographic proof of erasure.
You walk away with a real read on fit. We walk away with enough to scope a proposal. Either way you'll know more than when you started.
Book discovery