- Consumer-permissioned aggregation: customers, accounts, available and live balances, transactions and refreshes
- Account-owner verification and recurring-transaction detection for onboarding and underwriting
- Pay-by-bank (ACH) and lending-data routes alongside the aggregation surface
- Not a card gateway: no PAN or CVV ever involved; data is subject to US consumer-permission and FCRA rules
- Iris obtains the two-hour Finicity-App-Token with your partner id and secret; the app key is sent as a header per request
Mastercard Open Finance API Connector
Mastercard Open Finance (Finicity) for the US market — consumer-permissioned account aggregation, balances and transactions, account-owner verification, pay-by-bank and lending data — connected to Apivom Iris with your Mastercard Developers partner credentials; Iris mints the app token, Apivom stores no secret.
What you can do
Use cases
- Verify the bank account before the first payout — Confirm account ownership and current balance for a new US customer or vendor from Iris before you release an ACH payment to them.
- Cash-flow view for underwriting — Pull transaction history and recurring-transaction detection for a permissioned account to support credit decisions kept on the customer's Iris record.
- Pay-by-bank without card fees — Offer ACH pay-by-bank to US customers through your Mastercard Open Finance agreement, with the payment record and status maintained in Iris.
Mastercard Open Finance — the former Finicity platform — gives US businesses consumer-permissioned access to bank data: the account holder links an institution, after which the API returns accounts, available and real-time balances, transaction history, recurring-transaction detection, account-owner details for verification, pay-by-bank (ACH) capabilities and lending-oriented reports. Apivom Iris connects to it as a selectable payment provider. The credential is your Mastercard Developers partner id, partner secret and app key; Iris performs the authentication call to mint the short-lived Finicity-App-Token itself and forwards it, together with the app key header, on every request through Apivom Atlas — so the partner secret never leaves your tenant and Atlas stores nothing. This is not a card-payment API: no card number or CVV is ever handled, but the data is consumer-permissioned and, for lending use, governed by US FCRA obligations that remain yours. Any catalogued route can be run by an administrator from the Iris integrations hub — reads directly, writes behind a confirmation — with request and response logged in your tenant. Inbound webhook signature verification for this provider is not enabled yet; notifications are rejected until it is.
Mastercard Developers partner id + partner secret + app key. Iris swaps id and secret for a Finicity-App-Token (≈ 2 h) and sends it with the Finicity-App-Key header per request. Secrets are encrypted in your Iris tenant; Atlas stores nothing. Webhook signatures are not yet verified (fail closed).
Frequently asked questions
Is this a card-payment integration?
No. Mastercard Open Finance is account aggregation, verification and pay-by-bank over consumer-permissioned bank data. No card numbers are involved, so it does not add PCI card scope; it does carry US consumer-permission and, for lending, FCRA obligations that stay with your business.
How does the app token work?
Iris calls Mastercard's partner authentication endpoint with your partner id and secret and receives a Finicity-App-Token valid for roughly two hours; it caches the token and sends it, with your app key header, on each request. The secret never leaves your tenant.
Are webhooks processed?
Not yet. The per-tenant receiver exists but signature verification for this provider is not enabled, so inbound notifications are rejected (fail closed) until it is; state is read through the API in the meantime.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.