Two ways to pay.
One real order.
Card and pay-on-delivery are both first-class here — not a proper checkout with a cash afterthought bolted on. Either way the order is recorded the same, tracked the same, and receipted the same.
- Card
- Held until delivery
- Pay on delivery
- Never touches the wallet
- Account
- Not required to buy
What changes
A transfer screenshot is not a receipt.
The most expensive moment in a chat sale is the one where somebody has to decide whether to trust the other person. Checkout removes the decision.
Without it
- A screenshot you have to squint at and believe
- You ship and hope, or stall and lose the sale
- Delivery fee argued out message by message
- No order number, so “which one?” starts every reply
With Traxease
- A verified payment, confirmed by the processor
- The money is held — safe for them, promised to you
- Delivery priced by the zone before they pay
- An order number, a status and a receipt from the first second
Run one through
Send an order down either lane.
Pick a payment method and watch the same basket settle two entirely different ways. The lane that touches your wallet, and the lane that never does.
The basket
- Emerald wrap dress × 1₦45,000
- Linen shirt · sand × 1₦28,500
- Delivery · Enugu metro₦2,500
- Total₦76,000
Your wallet
Pending
₦0
Available
₦0
Card sales land here as pending, then release.
Choose a payment method to send this basket down its lane.
A model of the real flow, running in your browser. No payment is created and nothing is charged.
How it works
From basket to recorded order.
Hover a step to follow the thread. The first three are identical for both lanes; only the last one differs.
A cart survives without an account
Guests are given a cart token, so a shopper can fill a basket, close the tab and come back to it without ever signing up. Making people register before they can buy is how you lose the sale.
Delivery is priced by your zones
You define the areas you deliver to and what each costs. The fee is added before payment, so nobody is surprised at the door and nobody has to negotiate it in a chat.
Coupons are validated server-side
A code is checked against its real limits — window, usage cap, minimum spend — on the server. A discount cannot be forced by editing anything in the browser.
The lanes settle differently
A card payment is verified with the processor and lands in your wallet as pending, held until delivery. Pay-on-delivery records the order and stops: no wallet movement, no commission, nothing held.
Specification
What checkout does and does not do.
Including the parts that would be easy to quietly not mention.
- Card payments
- Processed server-sideKeys never reach the browser
- Card settlement
- Held as pendingReleases on delivery, or after 7 days
- Pay on delivery
- No wallet movementYou are paid directly; nothing is commissioned
- Guest checkout
- SupportedCart token — no account required to buy
- Delivery fees
- Your shipping zonesPriced before payment
- Coupons
- Validated on the serverWindow, usage cap and minimum spend enforced
- Confirmation
- Signed webhookHMAC-SHA512 verified and deduplicated
- Processing rate
- Set by the processorWe do not add a percentage to it
- Receipt
- Issued on both lanesPlus a tracking page per order number
Pairs with
None of this works alone.
Each capability assumes the others exist. These three are the ones this page leans on most.
Take a real payment this week.
Both lanes are on by default. Choose the ones you want, set your delivery zones, and send someone the link.
Free to start · No card required

