Meet cart-pal
Security-first commerce, from checkout to fulfillment.
The merchant problem
A sale can leave staff juggling payment checks, order entry, warehouse messages, and shipment updates. cart-pal connects those handoffs in a deliberate workflow so the team can see what happened and what needs review.
Who it is for
Our initial focus is home, gift, stationery, lifestyle, and branded-merchandise businesses shipping physical goods. Start with one merchant and one fulfillment provider. Exact catalog eligibility and integration fit require review.
What the simulation demonstrates
Build a basket, choose approved, declined, or uncertain, then follow the order. A decline creates no paid order or shipment. An uncertain result waits for review of the original payment. A warehouse pause leaves the paid order queued. All activity is fictional and clears on reload.
Implemented; merchant validation pending
The software includes NMI-hosted card tokenization, server-owned pricing, a stable checkout key for duplicate-request safeguards, explicit uncertain outcomes, reconciliation endpoints, payment audit events, and durable fulfillment handoffs. Merchant sandbox and warehouse acceptance remain outstanding.
Before production
Merchant sign-in, defined roles, tenant isolation, operator identity, monitoring, backup checks, incident response, and rollback must be validated. Assign owners for refunds, disputes, fraud, and support. Require documented acceptance and a go/no-go review before live activity.
Agent checkout: proposed direction
Evaluate human review of uncertain payments, revocable agent credentials and spending limits, authorization standards, actor-aware audit records, and agent-specific traffic controls. These are proposals, not available features, compatibility claims, or delivery commitments.
Commercial starting point
Illustrative software pricing is $149/month plus $0.25 per billable order: $274/month at 500 orders, before setup and other costs. This is not a quote. Scope integration, support, processing, fulfillment, and postage separately. Payment revenue requires a written partner agreement.
Trust and privacy
The public simulation collects no card or personal details and makes no payment or warehouse requests. The pilot brief is generated on the visitor's device. Hosting/security providers may process technical request data. NMI discussions are exploratory; no endorsement, signed partnership, production approval, or PCI certification is claimed.