PRODUCT · SCREEN

GateGraph: customer relationship graph

Your tenant's own relationship graph: which customers share wallets, addresses, devices, IPs, bank refs or card / IBAN tokens.

Start free sandbox Talk to us50 screenings a month free, no card.

On this page

GateGraph in simple terms

GateGraph connects your own customers through what they share: the same wallet, device, internet address, bank account or card. If three supposedly unrelated customers use one phone, you see it.

It only uses data you already send, and it never links your customers to anyone else's.

IN EVERYDAY TERMSThink of a hotel noticing that three guests who checked in under different names all drove up in the same car.

What it does

GateGraph is your tenant's own relationship graph, built from what you already send: registered wallets, funding-event addresses and transaction hashes, screenings with a customerRef, reconciliation processor ids, plus device id, IP, bank reference and the hashed card / IBAN token (instrumentRef) on funding events, crypto or fiat, when you include them.

For any customer it lists their attributes and every other customer of yours touching the same attribute. Nothing crosses tenants, and nothing is inferred from the blockchain.

Why a broker needs it

Mule patterns are structural: one wallet funding many accounts, several accounts paying out to one destination, a device or bank account shared across supposedly unrelated customers. None of this is visible from a single screening or on-chain. It needs your account data joined with your funding data, and supervisors expect the broker itself to be able to show that link.

How it works

GET /api/v1/customers/{ref}/graph returns the customer's attributes and the customers that share each one. The Behaviour Engine reads the same graph at screening time and adds a network link signal (device/IP 55, bank reference or payment instrument 60, shared funding address 50); a shared registered wallet is already the 70-severity shared-wallet signal. The console shows the same view on the customer.

What it does not do

GateGraph does not cluster addresses on the blockchain, does not label exchanges or services, and never links customers of different tenants. It knows only the attributes you sent; a device id you did not include is a link it cannot see.

API

GET /api/v1/customers/cust-8812/graph
{
  "customerRef": "cust-8812",
  "nodes":  [ { "id": "…", "kind": "address" | "device" | "ip" | "bank" | "instrument" | "processorTx" | "tx", "label": "…" }, … ],
  "edges":  [ { "from": "customer:cust-8812", "to": "…", "via": "registered_wallet", "at": "…" }, … ],
  "linked": [ { "customerRef": "cust-9105", "shared": [ { "kind": "device", "label": "…", "via": "…" } ] } ],
  "depthNote": "…", "signal": { … }        // the network-link signal the Behaviour Engine would emit
}

Full reference: /docs#graph · OpenAPI 3.1

Start free sandbox Read the API docs Talk to us