Receive calls from Moov Money
When your integrator hosts an FI’s ledger endpoints, configure the FI to route its calls to your receiver. Each FI keeps its own configuration and signing secrets.
Use the shared FI receiver contract for the request and response envelopes, operation fields, encryption, and endpoint checks:
- Funding setup explains how to configure the four URLs, create a signing secret, and verify the endpoints.
- Ledger endpoints describes authorize, capture, release, and credit.
- Encryption covers the JWE format and optional OAuth client credentials.
If one receiver URL serves several FIs, use the protected JWE header’s
kid to select the signing secret. It is the ID of that secret. After
decrypting the request, check that its providerID belongs to the FI
associated with the secret. The FI API reference describes the
request envelope and
signing-secret operations.
When you require OAuth, create credential references under the account
that owns the routing values. If your integrator account owns the
receiver configuration, it owns those references. Each FI registration
uses its own credential reference and receiver-issued client ID. Use
the returned jwksURL as-is. Encryption covers
the owner-specific JWKS route, cache lifetime, and key rotation.