INTEGRATION EXPERIENCE

Providers and systems
referenced in our work.

Historical references from our product and project descriptions, grouped by the role each organization or standard plays.

The names below are historical integration and domain references. They do not establish an official partnership, endorsement, certification, or a currently available connection. Scope and provider status are confirmed for each project.

Payment providers & processing

CardConnectStripeWorldpayi2cVantiv (historical name)LUUPDixiPay

Identity, screening & business information

LexisNexisWorld-CheckMelissaNafathSIMAHQawaemTahaqaq

Networks & ecosystems

MastercardUnionPay

Reference lists, standards & regulatory context

OFAC sanctions listsPCI DSSSAMA
Different organizations have different roles.

Networks and standards are not customers. OFAC lists are screening references, PCI DSS is a security standard, and SAMA is a regulator. Their inclusion does not assert approval. SWIFT, SEPA, and IBAN-related engineering is provider-connected and scoped to contracted access.

INTEGRATION ENGINEERING

What we check
before an integration

We agree how the systems communicate and what should happen when a request is late, duplicated or unsuccessful.

  • Authentication, tenant boundaries, and data ownership
  • Timeouts, retries, callbacks, and idempotency
  • Provider states and financial reconciliation
  • Test evidence, operational handover, and change support
Discuss an integration

YOUR CHOICE

This website uses no analytics or advertising trackers. If you save a preference, it is stored only in this browser.

Both choices keep optional tracking off because none is configured. Read how this website uses storage.