Your money moves through an account that belongs to somebody else. You are a sub-account, and the reserve, the review and the shut-off switch are all theirs. Instead: a dedicated merchant account in your own entity, underwritten in your name, with you as the merchant of record.
Everything you sell goes down a single processing route. When that route pauses, the business pauses with it and there is nowhere for the next order to land. Instead: more than one merchant account, live at the same time, with the volume weighted between them.
Shifting volume, checking a payout, chasing a hold that nobody told you about. All of it manual, all of it after the fact. Instead: the routing runs on its own, and every payout is checked against what was expected before anyone thinks to look.
The card is entered, the payment goes down whichever rail carries the most weight, it lands, and it settles. You can add a rail, drop one or change the weighting without rebuilding anything around it. Then the payout that arrives is compared with the payout that was due.
BLCKLDGR holds and administers the vault contract. The merchant's card data remains the merchant's.
The merchant may direct a full export to any PCI DSS Level 1 provider on 30 days notice, for no fee, including on termination and including to a direct competitor of BLCKLDGR.
The merchant may add, remove or reweight any connected processor.
Access and export rights survive termination with a named administrative continuity contact.
Raw card numbers never touch BLCKLDGR systems. Card entry runs through the vault provider's hosted fields.
Payment holds and freezes remain possible. What changes is the blast radius: no single freeze takes the business down, and you see it the morning it happens.
Your access and export rights continue after termination, with a named administrative continuity contact written into the agreement. You can direct a full export of the vault to any PCI DSS Level 1 provider on 30 days notice, at any time, for no fee, including to a direct competitor of ours. The clause is there so that leaving is a decision you make, not a favour you ask for.
You will own this, including against us. The founder runs his own stores on the same stack, so the same rails collect our money before they collect yours. Twelve merchants came to us mid-freeze, twelve merchant accounts were boarded in their own entities, and all twelve are still trading.
You own the exit, including against us.
One screen instead of five dashboards and a spreadsheet. Everything you already run reports into one record, in one place, and every figure keeps the name of the system that reported it.
Your settlement cycle repeats, so the date and the amount of the next payout are known before it arrives. These are the conditions that set off an alert, and this is how each one reaches you.
| Condition | Severity | Delivery |
|---|---|---|
| Payout absent more than one business day past expected | S1 | SMS |
| Amount short by more than 20% with no known reserve change | S1 | SMS |
| Account status change, new hold flag, or reserve applied | S1 | SMS |
| Payout late within one business day | S2 | Email + in-app |
| Amount short 5 to 20% | S2 | Email + in-app |
| Expected batch did not close | S2 | Email + in-app |
| Baseline drifting, or a ratio approaching a threshold | S3 | In-app |
Revenue, spend, contribution and open alerts.
Authorization, declines, settlements and expected versus actual payouts by rail.
Revenue by funnel, lander and offer with the collecting rail.
Rebill health, involuntary churn and recovered revenue.
Ratios, disputes by stage and reserve exposure.
Protected recurring revenue, vault coverage and failover record.
COGS, freight and landed cost by SKU.
The cockpit reads the systems you already run, plus your dispute, 3PL and freight feeds. Nothing here asks you to drop a tool that works.
Every figure keeps the source that reported it. The ad platform says this, the gateway says this, the CRM says this. Four versions of the same money are never quietly compressed into one number and handed to you as the truth.
We charge for the platform and for the work. We don't hide our margin in your rate. The rate is interchange plus a disclosed markup, quoted only after we read three months of your statements, and it comes down as your volume goes up.
Quoted as a figure before anything is built, and reduced against the rails commitment. The range is published on the migration page.
A monthly fee, priced on the size of the business rather than on how much of the system you are allowed to see.
Migration, boarding and the operating work are scoped and priced in writing before any of it starts.
Interchange plus a markup you can see. It is not where this business makes its money, and it comes down as your volume goes up.
Three months of processing statements is the only way to know what you are paying now, and whether a better deal exists at all. If it does not, we tell you.
What the rails collect goes back to the layer that made the decision. The loop closes when what actually happened changes what you do next.
Open INTELLIGENCE↗