Sandbox
Explore the public contract with isolated test value and build a proof pack. Production use, contractual support, and an SLA are not included.
Open SandboxEvaluate the public contract without a production commitment, then document the usage, implementation, support, assurance, and exit terms your launch requires.
Explore the public contract with isolated test value and build a proof pack. Production use, contractual support, and an SLA are not included.
Open SandboxA fixed-scope, 6–8 week Sandbox evaluation for one existing program, one proof loop, synthetic nonfinancial test records, and a written migration decision. The starting figure is nonbinding and subject to an accepted statement of work.
Request a pilot fit reviewAvailable only after separate technical, commercial, security, privacy, support, usage, and readiness review. The pilot does not include or entitle Production activation.
Discuss open production gatesprogramOne current program, approximate record volume, source rules, reward and return policy, control totals, and the decision trigger.
test dataSynthetic, nonfinancial opening-position records only. Real or pseudonymized customer data requires separately executed privacy and security terms.
proof pathThe published API or integration starter, merchant-owned commerce and identity adapter, acceptance cases, and evidence owners.
decisionStop criteria, exception thresholds, required reviewers, open connector or assurance gates, and the expected stop, extend, or proceed memo.
commercialFinal scope, schedule, price, payment terms, responsibilities, change control, support boundary, and portable-exit terms.
The public $15,000 figure is a nonbinding starting price for the fixed Reconcile & Launch evaluation scope. It is not a checkout price, guaranteed quote, Production entitlement, generally available SaaS list price, volume discount, contractual SLA, response-time commitment, service credit, or termination-assistance rate. Final pilot, Production, and enterprise terms become commitments only when written into an executed agreement.
Name the current program, approximate balance-record volume, decision trigger and date, available synthetic test evidence, and any connector or assurance requirement that could block the evaluation. Do not include customer data or credentials.