Commerce & Payments · Integration
Tapfiliate
Add Tapfiliate to your product for your customers, and give your AI agents governed access to it.
Tapfiliate versions its API in the path at api.tapfiliate.com/1.6 and authenticates with an X-Api-Key header. The object that matters is the conversion: you post it with your own order identifier and an amount, and Tapfiliate then generates one commission per matching rule, so a single order can produce several commission records that are approved or disapproved individually. Affiliates exist at account level and are joined to a program as a separate step, so creating an affiliate does not by itself place them in one. Customers are tracked so recurring commissions attribute back to the original referrer, which is why replaying historical orders can pay twice unless the external identifier is reused. It is filed under commerce because conversions, commissions and customers are the real objects, even though the product is sold as affiliate marketing. fastn holds each customer's Tapfiliate key in its own tenant and keeps the conversion mapping working.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Tapfiliate account so your checkout posts conversions into their program
Create affiliates and add them to the right program when a partner is approved in your product
Show a partner their commissions and approval state inside your own dashboard instead of Tapfiliate's
Reconcile refunds by disapproving the specific commissions tied to a cancelled order
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent approve or disapprove commissions against a stated rule, with the conversion and commission IDs logged per tenant
Have an agent find conversions posted without a customer reference so recurring attribution can be fixed
Let an agent answer a partner's question about why a commission was calculated at a given rate
Example prompt
Which affiliates drove the most approved commission value last quarter?
Set up Tapfiliate in 4 steps
- 01Enable the Tapfiliate connector from your fastn dashboard.
- 02Have each customer authorise their own Tapfiliate account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Tapfiliate integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Tapfiliate integration without building it. Your customers connect their own Tapfiliate 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 Tapfiliate update is not your on-call problem.
- One integration serves your product and your agents. The same governed Tapfiliate 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
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Tapfiliate, across other categories.
NetSuite
Notion
Box
DocusignTapfiliate integration FAQ
How do I add a Tapfiliate integration to my product?
Enable the Tapfiliate connector in your fastn dashboard, then let each customer authenticate their own Tapfiliate account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Tapfiliate client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Tapfiliate account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Tapfiliate 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 Tapfiliate integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent approve or disapprove commissions against a stated rule, with the conversion and commission IDs logged per tenant
Who maintains the Tapfiliate integration?
fastn does. When Tapfiliate 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 Tapfiliate 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 Tapfiliate integration?
A common starting point: let a customer connect their own Tapfiliate account so your checkout posts conversions into their program. 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 Tapfiliate integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Tapfiliate does not change your per-connector cost. You can start free with 3 connected accounts.
Add Tapfiliate to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.