Skip to content

Integrations

Integration mapOn the left, systems connected in the institution's name: FundConnext, TRADE CORE, email and SMS providers, NDID and DOPA; on the right, the liveness and face-match service connected in QX's name, the FATF website, and AMLO's AERS, where officers file by hand.IN THE INSTITUTION'S NAMEIN QX'S NAMEFILESFEED ⇄ ORDERSNOTICESIDENTITYDAILYBY HANDMODULECDD COREofficer consolePRODUCTKYC COREapplicant appFundConnextcustomer & account files · statementsTRADE COREDA Dealer onlyEmail · SMSin the institution's nameNDID · DOPAidentity proofing · card checkone link per institutionFATF websitecountry list checked dailyAMLO AERSno system-to-system linkLiveness · face matchinside the application pageLEGENDConsoleExternal systemAPI / fileManual step
Left: connected in the institution's name. Right: the liveness service in QX's name, a public source, and AERS, where officers file by hand.

Message formats, keys and error codes are in the API reference.

Some connections are a right of the institution as a reporting entity. NDID, DOPA and AMLO’s systems connect only authorised parties. These are always connected in the institution’s name: QX connects as its outsourced IT provider, separately for each institution, and never shares one connection across institutions.

Others are part of the product. The liveness and face-match service is connected in QX’s name, and QX carries the vendor relationship.

SystemUsed forDirectionNotes
FundConnextCustomer and account files; monthly statement filesInFetched automatically or imported by officers
TRADE CORE (DA Dealer)Transaction feed and execution confirmations in; customer status, restrictions and limits outBothQirin X’s TRADE CORE, run in the institution’s own environment
NDID · DOPAIdentity proofing and ID card check during account openingBothIn the institution’s name; one link per institution
Liveness · face matchLiveness and face match during account opening and signingBothIn QX’s name; runs inside the application page
Email · SMSNotices to applicants and customers; one-time codesOutSent in the institution’s name, with its own provider keys
FATF websiteDaily check of the high-risk country listsInA change takes effect only after approval
AMLO AERS——No system-to-system link; officers file. DA Dealer files are prepared as AERS XML
  1. The institution confirms which connections it holds, or will apply for.
  2. For connections in its name, the institution grants QX the authority to act as its provider, for example a power of attorney for DOPA.
  3. QX builds the connection for that institution only, keeps its keys apart from every other institution and tests it before go-live.
  4. Each connection’s status is recorded in the institution’s installation annex.