Portable package

PushFi → Maia integration package

One archive containing the API contracts, machine-readable schemas, the full field mapping and calculation semantics, credential-binding requirements, the operations spec and all 12 synthetic fixtures as individual JSON files.

HMB hold active
Scenario 3690809 inactive
Synthetic data only
No secret in archive
Contract v2.0

pushfi-maia-integration-package-v1.0.zip

21 files · 91.4 KB · guide + 9 documents + 12 fixtures

Archive contents
README.md
6.0 KB
01_API_CONTRACTS.md
13.6 KB
02_SCHEMAS.json
18.3 KB
03_FIELD_MAPPING.md
7.4 KB
04_CALCULATION_SEMANTICS.md
10.2 KB
05_CREDENTIAL_SETUP.md
6.4 KB
06_ERRORS_IDEMPOTENCY_RECOVERY.md
8.2 KB
07_DEPLOYMENT_STATUS.md
7.0 KB
manifest.json
4.8 KB
fixtures/*.json12 files, one per fixture
9.6 KB
What Maia may wire

Callable: getExistingCreditResult — a pure read. makeLeadsApi for intake.

Not callable: getCreditAuthorizationState (staff session) and triggerCreditPull (internal credential, plus the HMB hold). Both are documented, not authorised.

Unresolved, deliberately

8 of the 9 credit attributes have no existing Acqualify input slot; two of them would corrupt figures if mapped by name similarity.

Revolving balance, utilization, inquiries, credit tier, mortgage payment and derogatory composition are marked UNRESOLVED rather than substituted. A stale value is a decision; a mislabelled one is a defect nobody sees.

Status carried inside the archive

Read endpoint live and verified on the published host.

HMB_OUTBOUND_RELEASE_HOLD = true, unchanged.

Credential contract: 16 / 16 passed, 0 provider calls.

Credit-reuse suite: 23 / 23 passed, 0 writes.

Release gate on the published host: PASS.

Blueprint certificate: operator-attested only, not verifiable from here.