UDA connector — overview

The UDA connector is Ark's core-banking connector. It exposes Ark's banking connector contracts and fulfils them against ULTRACS (the UDA core-banking system) over SOAP. It is the downstream integration for accounts, cards, parties, payees, payments, statements, products, and the admin id-mapping surface.

The connector is a thin mapping layer: it stores only the mapping between Ark ids and ULTRACS ids (plus product / card-product / transaction-type reference data), and reads the banking data live from ULTRACS on each call. ULTRACS identifies a customer by its own client key, which the connector resolves from the local party mapping using the platform partyId.

Resource groups

Group	Routes under	What it covers
accounts	/v1/accounts	list/detail, open savings account, set nickname, transactions + detail, signatories
cards	/v1/cards	list/detail, order, activate, lock/unlock, cancel, transaction settings
parties	/v1/parties	create/get/update party, relationships, scheduled payments, search
payments	/v1/payments	BSB lookup, BPAY biller lookup/search, PayID alias resolution, validate, initiate
payees	/v1/payees	list/detail, create, delete
statements	/v1/parties/statements	list, download (PDF)
products	/v1/products	list, create or update (catalogue)
admin	/admin/mapping	internal id-mapping read/write (writes Ark↔vendor bindings)

Per-group call contracts are in the endpoints reference; deep internals are in the architecture reference (one file per group).

Where to read next

You want…	Doc
How to call the API	endpoints (non-dev)
Card states + party provisioning	lifecycle (non-dev)
How it's built + per-group internals	architecture (dev)
How to build, run, test, regenerate	development (dev)
Quirks, gaps, known issues	notes (dev)

The formal request/response contracts are the OpenAPI specifications under openapi/source/connector/ (accounts, cards, parties, payees, payments, products, admin); this doc set does not restate them.