Reference & Lookup Data · Integration
Mastercard
Add Mastercard to your product for your customers, and give your AI agents governed access to it.
Embed a Mastercard integration so your customers use their own Mastercard developer credentials from inside your product rather than a shared key you have to meter, rotate and defend. Mastercard exposes its capabilities as a set of APIs, and fastn holds each customer's credentials per tenant, handles signing, retries and rate limits, and logs every call so a request can be traced back to the event that caused it. Writes are idempotent, which matters more here than almost anywhere else: a retry after a timeout must not apply the same operation twice. The same governed connection powers in-product features and gives your AI agents scoped, audited access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Mastercard credentials so calls run under their agreement and entitlements rather than yours.
Trigger a Mastercard call from an event in your product, with idempotent writes so a retry cannot apply the same operation twice.
Read transaction detail back into your product so a user can reconcile against the record that created it.
Keep every call logged per tenant so a request can be traced to the customer and the event behind it.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up transaction detail for one customer within scoped permissions, with the read audited.
An agent gathers the facts behind a disputed transaction and hands the decision to a human.
An agent reconciles what your product recorded against what Mastercard returned and reports the differences.
Example prompt
Pull the transaction detail behind this charge and tell me whether it matches what we recorded.
Set up Mastercard in 4 steps
- 01Enable the Mastercard connector in your fastn dashboard.
- 02Have each customer supply their own Mastercard credentials so calls run under their account.
- 03Map the operations and fields your product uses, then enable only the scopes you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Mastercard integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Mastercard integration without building it. Your customers connect their own Mastercard account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Mastercard update is not your on-call problem.
- One integration serves your product and your agents. The same governed Mastercard connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Works well with
Stripe
Adyen
CybersourceOften used alongside
Tools the same teams tend to run next to Mastercard, across other categories.
Salesforce
HubSpot
Notion
SnowflakeMastercard integration FAQ
How do I add a Mastercard integration to my product?
Enable the Mastercard connector in your fastn dashboard, then let each customer authenticate their own Mastercard account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Mastercard client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Mastercard account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Mastercard account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Mastercard integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent looks up transaction detail for one customer within scoped permissions, with the read audited.
Who maintains the Mastercard integration?
fastn does. When Mastercard changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Mastercard lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Mastercard results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Mastercard is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Mastercard integration?
A common starting point: let each customer connect their own Mastercard credentials so calls run under their agreement and entitlements rather than yours. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Mastercard integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Mastercard does not change your per-connector cost. You can start free with 3 connected accounts.
Add Mastercard to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.