A pre-charge screening API for Caribbean merchants. One HTTPS call before you charge the card returns block or allow in under fifty milliseconds. When one merchant reports a chargeback, every connected merchant inherits the protection.
Two required fields. One response field. No SDK, no webhook receiver, no PCI scope expansion. The contract has been deliberately kept this small so you can ship in an afternoon and never come back to maintain it.
Optional fields enrich the score and the network signal — email, phone, card_fingerprint, delivery_lat/lng. Send what you have; we match against what's there.
// Before charging the card: $response = $http->post('https://api.trustbarrier.tech/v1/check', [ 'headers' => ['Authorization' => "Bearer {$TB_KEY}"], 'json' => [ 'ip' => $customer->ip, 'address' => 'LG Smith Blvd 101', ], 'timeout' => 2, ]);
{
"decision": "allow",
"reason_codes": [],
"score": 0,
"event_id": "ev_01HF8KZX9PMQ4YRTBN3W7K2A6V"
}
Read decision. If "block", decline the order. Otherwise, charge as you would today.
Generic global vendors price for Fortune 500 transaction volume and miss the patterns specific to small-island commerce. TrustBarrier was designed from day one for markets where addresses are free-form, telecom carriers are concentrated, and the same fraud actors hit every merchant in turn.
Carrier-grade NAT means a single IP can mask tens of thousands of legitimate customers. The engine carries a curated registry of protected ISP ranges, so you never lock out a real buyer because of how their carrier routes traffic.
A chargeback at one merchant becomes a signal at every other. Reported signatures — IP, address, card fingerprint, email, phone — propagate through a curated global pool within minutes, with merchant-controlled opt-in.
The contract is two required fields and one response field. There is no SDK to vendor, no event bus to wire up, and no PCI scope to revisit. If your checkout already does an HTTPS call, you can ship TrustBarrier today.
TrustBarrier is a pre-authorisation screening layer. It does not replace 3DS, it does not replace your gateway, and it does not see PAN, CVV, or track data. The integration touches one path in your checkout — the moment between order capture and the call to your processor.
Hard rules block on definitive matches — known bad IP, address, email, phone, or card fingerprint. Everything else feeds a score from a fifty-point baseline. Cross your threshold and the decision flips to block; stay below it and the response is allow with the contributing signals attached for your audit log.
Every block decision on any merchant on the network feeds back into the score for the next thirty days. The first merchant pays the cost; everyone else inherits the protection automatically. No reports, no exports, no manual sharing.
A request IP that has been blocked by three or more merchants in the last twenty-four hours is treated as compromised infrastructure, not a customer. Catches the IP rotation that single-merchant velocity rules miss.
Any identifier — card, email, or phone — sitting on another merchant's local blocklist contributes weight even before a chargeback is filed. The network is loud well in advance of any individual merchant's first loss.
The classic gmail dot-and-plus trick — john.doe+x@gmail.com versus johndoe@gmail.com — collapses to one inbox in the matcher. Outlook, iCloud, Proton, FastMail, and Yahoo aliases are handled per their documented rules.
A small character-edit on a blocklisted address — a missing letter, a transposed digit — still triggers a soft signal. Exact matches stay on the hard-rule path; near-misses lift the score without false-positiving the neighbour next door.
A curated registry of roughly five hundred throwaway-mail providers, refreshed against the public lists and tunable per merchant. Mailinator, Guerrilla, ten-minute mail, and the long tail of self-hosted clones all surface as a soft signal, never an automatic block.
Sliding-window counters on the same IP, card fingerprint, or email address. Eleven attempts from the same IP in five minutes, or six different cards on the same email in an hour, are flagged before the decline rate has a chance to climb.
A single browser fingerprint paired with two or more distinct emails or cards on the same merchant inside thirty days is the canonical sock-puppet pattern. The signal scales with the number of fresh identities tied to that one machine.
PCI-clean: brand, BIN, last four, and expiration — exactly the fields your processor already exposes. A reissued card with a fresh expiration is a separate signature, not a stale block. The engine never blanket-blocks on BIN alone — that would lock out an entire issuing bank.
Every fired signal is returned in the API response and captured in the immutable audit log. You see exactly which weights moved the score, with no black-box scoring decisions you cannot defend in a chargeback dispute.
The first cohort of merchants is being onboarded now. A short call, an account, an integration guide — and screening starts.