Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Integration Points

SNA defines 8 integration points, labeled A through H, corresponding to the 4 interface points: one on the AA-FIP side and one on the AA-FIU side of AA's service. Each point represents a direction of data flow that SNA monitors.

Integration Points Summary

Point
Direction
Side
SLA
Billing
SaaNs
MIS

A

requestOut

AA-FIP

✔ Required

✔ Required

✔ Required

B

responseIn

AA-FIP

✔ Required

✔ Required

✔ Required

C

requestIn

AA-FIP

✔ Required

✔ Required

✔ Required

D

responseOut

AA-FIP

✔ Required

✔ Required

✔ Required

E

requestOut

AA-FIU

✔ Required

✔ Required

F

responseIn

AA-FIU

✔ Required

✔ Required

G

requestIn

AA-FIU

✔ Required

✔ Required

H

responseOut

AA-FIU

✔ Required

✔ Required

Integration Point Details (AA-FIP Side)

Point
Direction
What to Capture

A) requestOut

AA → FIP

Capture outgoing request data: API type, timestamp, target FIP ID, request size

B) responseIn

FIP → AA

Capture incoming response data: HTTP status code, response time (ms), response body size

C) requestIn

FIP → AA

Capture incoming FIP notifications: API type, timestamp, source FIP ID

D) responseOut

AA → FIP

Capture outgoing response data: HTTP status code, timestamp

Integration Point Details (AA-FIU Side)

Point
Direction
Applicable APIs
What to Capture

E) requestOut

AA → FIU

/Consent/Notification, /FI/Notification, /Heartbeat

Outgoing request data: API type, timestamp, target FIU ID

F) responseIn

FIU → AA

Responses to the APIs at point E

Incoming response data: HTTP status code, timestamp

G) requestIn

FIU → AA

/Consent, /Consent/handle, /Consent/fetch, /FI/request, /FI/fetch, /Consent/Notification¹, /FI/Notification¹

Incoming request data: API type, timestamp, source FIU ID

H) responseOut

AA → FIU

Responses to the APIs at point G

Outgoing response data: HTTP status code, timestamp

¹ ReBIT specifications allow these notifications to be sent to the AA by an FIU. Capture them only if your AA supports receiving them

📌 Some APIs also require additional attributes (addlAttr) on both the AA-FIP and AA-FIU interfaces

Last updated

Was this helpful?