What an API adapter is
We mapped our API calls onto theirs. Every operation your vendor exposes — create an order, check an order, read a balance — has a Fluz operation behind it, and the adapter sits in between doing the translation in both directions. The result is that the integration you already built against Tango, Runa, or InComm now buys from Fluz instead. You keep your request shapes, and a successful response comes back in the shape your parser already expects. Two things are Fluz’s rather than your vendor’s: error responses and order status values. Both are covered in Connector behaviour.
Think of a travel plug adapter. The appliance does not change. The wall socket does not change. Something in between makes the two fit.
How the mapping works
Your request arrives shaped like the vendor’s. The adapter translates the route and the fields into the equivalent Fluz operation, executes it against Fluz supply, then translates the result back into the response shape your code already expects.
Operation mapping
Each connector page publishes the full table for its vendor. Tango Card, as an example:
Paths and verbs are preserved deliberately. The point of the adapter is that your routing layer does not have to know anything changed.
Field mapping
Tango Card again, as an example:Tango and InComm return complete results synchronously. The call does not return until the purchase has finished, which can take up to 150 seconds, so set your client’s read timeout above that. Runa is asynchronous by default: it returns a reference ID immediately and you read the order once it completes. Send
X-Execution-Mode: sync to wait for the full result instead. Both are covered in Connector behaviour.Per-vendor request constraints
Your vendor’s request shape is accepted as it stands, but a few values are fixed. Email delivery to the recipient must be off, orders are single-recipient and single-product, and Runa orders must be funded from the account balance in USD. A request that breaks one of these is rejected. The full list is on Connector behaviour. Read it alongside your connector page’s request examples before you cut over.What changes, and what does not
Brand identifiers are the one thing you must change. The adapter does not translate the vendor’s product catalog into Fluz’s. A Tango
utid of U561593 is not the same card as a Fluz utid of 1800FL-US. Map your brand list against the Fluz catalog before you cut over, or your orders will succeed and deliver the wrong card.Switching in three steps
1
Change the base URL
Point your existing client at the Fluz adapter host for your vendor. For Tango Card that is
https://api-adapter.staging.fluzapp.com/tangocard in staging and https://api-adapter.fluzapp.com/tangocard in production, instead of https://integration-api.tangocard.com/rass. Both hosts are listed on every connector page.2
Change the Authorization header
Every connector uses HTTP Basic authentication with your Fluz API key:
Authorization: Basic <FLUZ-API-Key>. Drop the vendor’s username and password.3
Remap your brand identifiers and send the same calls
Swap your vendor product codes for their Fluz equivalents. Everything else — paths, verbs, request bodies, response parsing — stays as it is.
Available connectors
Gift cards
Documented and available. Tango Card, Runa, InComm — each with a published endpoint comparison and request examples.
Payment processing
Beta. Stripe, Worldpay, TSYS, Checkout, Braintree, TabaPay, Finix, Authorize.net, Sola / Cardknox. Contact sales for early access and endpoint details.
Wallet withdrawals
Beta. Venmo and PayPal. Contact sales for early access and endpoint details.
Coverage is per-operation
The adapter implements the operations listed on each connector page, and only those. Each one is a purpose-built translation for that operation rather than a blanket pass-through.
Connectors are separate from the Fluz GraphQL API
This trips people up, so it is worth stating plainly. Fluz has two distinct developer surfaces, and they do not share credentials.Connector keys are not dashboard keys. The API key you generate in the Developers section of the Fluz dashboard will not authenticate against a connector, and vice versa. Connector credentials are provisioned by Fluz. Contact your Fluz representative to request one.
When to use a connector, and when not to
Use a connector when
You have a working vendor integration in production, you want Fluz supply and Fluz rates quickly, and you do not want to spend an engineering cycle on the switch. Time to live is measured in days.
Use the Fluz API when
You want the full platform: virtual cards, wallets and spend accounts, transaction data, webhooks, cashback rates, offer quoting, and the complete merchant catalog. None of that is reachable through a vendor-shaped interface.
Getting access
API Connectors are currently offered as a beta program. Contact your Fluz representative or email sales to request connector credentials and confirm operation coverage for your vendor.Pick your vendor
Tango Card
Orders and account balances. Basic auth, synchronous responses.
Runa
Orders and currency balances. Synchronous and asynchronous execution modes.
InComm
Immediate orders, order detail, card retrieval, and program balance.