One source file for every fact about the business
Legal name, publisher, excluded states and fees live in one configuration file, so a change is made once and appears everywhere, and a check can prove the page matches it.
BalanceSwap is a gift card exchange. A seller enters a card, gets a verified quote, and chooses cash or a cause. Behind the form sit identity checks, fraud controls, payment rails and the state by state rules that decide where the product may operate.
We built it to prove that a consumer product can launch with the controls a regulator expects on day one, rather than added after the first complaint.
The quote screen as it runs today. The balance is verified before an offer appears, and the seller chooses cash or a cause.
Nothing here is exotic. What is unusual is that the quote, the choice, the screen and the payout are separate records from the first transaction, so the operator can answer a complaint with evidence rather than a reconstruction.
The quote is built from a verified balance and a published rate, so the seller sees the same number the system will pay.
A seller can take the payout or direct it to a participating organization, with the designation recorded on the transaction.
Availability is decided state by state in configuration, not in marketing copy. Florida is excluded at launch.
Checks run before money moves. A failure stops the transaction and tells the seller why, within what the rules allow.
Payouts through a payment provider, with the provider's result stored per transaction rather than assumed.
Queues for review, holds and exceptions, assigned by role. The operator sees why a transaction stopped and what evidence sits behind it.
A marketplace that moves money is judged by what it refuses. The design decisions below are the ones a regulator, a payment partner and a defrauded customer would each ask about.
Legal name, publisher, excluded states and fees live in one configuration file, so a change is made once and appears everywhere, and a check can prove the page matches it.
The order of operations is enforced in the data layer. A transaction cannot reach payout with a failed or missing identity check, whatever the application code does.
Quote, choice, screen result, payout and provider confirmation are separate records. A correction after the fact is labeled as one.
Each release is verified on a phone width and a desktop width, with the rendered text checked against the configuration, before it is promoted.
Strip the gift cards away and this is a payments flow with an identity gate and jurisdiction rules. Banks, lenders, benefit programs and marketplaces all run the same three things.
Onboarding, disbursement, account changes. The gate is in the data layer, so the control is real rather than procedural.
Refunds, claims, disbursements and settlements that report what happened, not what was attempted.
Where you may sell, lend, quote or serve, held as data that is tested, rather than as a note in a policy binder.
Review queues that survive a change of staff, with the evidence behind each hold on the screen.
Thirty minutes. Bring the flow where money or identity has to be right, and we will tell you which parts of this apply and which parts do not.