Commerce & Payments · Integration
Tango Card
Add Tango Card to your product for your customers, and give your AI agents governed access to it.
Tango Card sends digital rewards, which means every write in this integration spends real money. The rewards-as-a-service API is built around accounts that hold funds, a catalog of gift cards, prepaid cards and donations that varies by country and value, and orders that deliver a reward to a named recipient by email or as a link. Idempotency is not a nicety here, because a retried order sends a second gift card and the money is gone. So orders carry a reference your product supplies, every call is logged per tenant against the account it drew on, and delivery status comes back as a webhook so your product knows whether the recipient got it. Each customer funds and authorises their own account, which is also how a platform keeps one customer's reward budget separate from another's.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer fund and authorise their own Tango Card account, so rewards come out of their budget rather than a pool of yours.
Read the catalog before you offer a choice, since which brands, values and currencies are available depends on the recipient's country.
Place an order with your own reference attached, so a retry after a timeout cannot send a second gift card.
Track delivery, resend a reward that bounced, and reconcile account balance against the orders your product placed.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports which rewards were sent this month, to whom, and against which account balance.
An agent places an approved reward order within scoped permissions, idempotently, with the reference recorded.
An agent finds rewards that were never redeemed and explains what to do about each.
Example prompt
How much of this account's reward budget is left, and which rewards sent last month are still unredeemed?
Set up Tango Card in 4 steps
- 01Enable the Tango Card connector in your fastn dashboard.
- 02Have each customer authorise and fund their own account, so orders draw on their balance and not a shared one.
- 03Map the catalog items, values and recipient fields your product uses, and set the reference every order carries.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Tango Card integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Tango Card integration without building it. Your customers connect their own Tango Card account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Tango Card update is not your on-call problem.
- One integration serves your product and your agents. The same governed Tango Card connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
StripeWorks well with
SurveyMonkey
QualtricsOften used alongside
Tools the same teams tend to run next to Tango Card, across other categories.
NetSuite
Notion
Box
DocusignTango Card integration FAQ
How do I add a Tango Card integration to my product?
Enable the Tango Card connector in your fastn dashboard, then let each customer authenticate their own Tango Card account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Tango Card client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Tango Card account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Tango Card account and only ever sees their own orders, payments and customers. 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 Tango Card 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 reports which rewards were sent this month, to whom, and against which account balance.
Who maintains the Tango Card integration?
fastn does. When Tango Card 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.
Is the Tango Card integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Tango Card integration?
A common starting point: let each customer fund and authorise their own Tango Card account, so rewards come out of their budget rather than a pool of 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 Tango Card integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Tango Card does not change your per-connector cost. You can start free with 3 connected accounts.
Add Tango Card to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.