Integration Flow
A complete integration is a five-step journey, tied together by the singletransactionId you receive from Consent Creation. Discovering your entitled FIUs is a
read-only reference call you can make at any point in this flow — even before your
first Consent Creation call.
1
Discover Entitled FIUs (reference)
Call List Entitled FIUs at any time to confirm which
fiuId values you’re
currently onboarded with, before naming them on Consent Creation. See
Entitled FIUs.2
Initiate Consent
Call Consent Creation with the customer’s details and the FIUs/products you
need data for, in one call. You receive a
transactionId and one combined
orchestrationWebUrl. See Initiate Consent.3
Redirect the Customer
Redirect the customer to
orchestrationWebUrl. They approve consent for every
named FIU on one combined screen, hosted entirely by MoneyOne. See
User Redirection.4
Track Status
Track each consent to a terminal state via Status Lookup — either polling with
just
transactionId, or batch-looking-up specific consents/sessions/handles. See
Track Status.5
Request and Fetch Data
Once a consent is approved, explicitly trigger a data pull with Data Request,
then retrieve the data with Get FI Data and derived insights with
Analytics. See Request Data and Fetch Data.
Pages in this section
Every endpoint requires HTTP Basic Auth (
client_id/client_secret, issued at
onboarding) — see each page above for its exact method, path, and headers.
Postman Collection
Import pre-configured API collection for testing
