FeelConnect▍
ProductsDocsPricingChangelog
Sign inGet API keys
FeelConnect▍

The developer-first financial data platform.

All systems operational

Products

Open banking APIBank data APITransaction enrichmentFinancial data APIPricing

Developers

DocumentationAPI explorerInstitution directoryDashboardGet API keys

Company

HomePlaid alternativeChangelogfeels.moneySign in

Legal

PrivacyTermsSecurityData processing
© 2026 FeelConnect. All rights reserved./v1 · FC-Version 2026-07-01
  1. FeelConnect
  2. Institutions
  3. Mercari
Mercari logo

// business platform · United States and Japan

Connect Mercari with the FeelConnect API

Mercari is in the institution catalog as inst_mercari. This page shows how it routes, what each connector in that chain can read, and the exact calls that start a connection.

institution_id
inst_mercari
type
business
countries
US · JP
auth
OAuth
mfa
Not expected
catalog status
healthy

Commerce, payroll, and accounting platforms that hold a balance or a transaction ledger. Link hands the user off to the institution's own consent page, so no password is ever seen by your servers or ours. No multi-factor step is expected in the normal flow, though a connector may still challenge.

// what you can read

Products available for Mercari.

Support is a property of the connector that serves the connection, not of the institution alone — so the honest answer is a matrix, not a badge.

Rows are this institution’s routing chain in order. Balances, transactions, assets, and recurring streams are available from every connector, because the last two are computed by FeelConnect from the first two. The rest exist only where the connector implements them.
ConnectorBalancesTransactionsRecurringAssetsIdentityIncomeLiabilitiesInvestmentsCrypto
PlaidagreementPlaid's sandbox is instant; Production access needs a company profile and a use-case review.
Sandboxself-serveAlways on. Deterministic simulated data — it never reaches a real institution.

At connect time the registry walks this chain and uses the first connector whose credentials are present in the deployment. Connecting Mercari to real data therefore requires the relevant provider credentials to be configured — without them the connection falls through to the sandbox, which serves realistic simulated data and never contacts Mercari. Test keys resolve to the sandbox regardless.

// Connecting Mercari for real

FeelConnect does not hold bank connections of its own. Every institution in the catalog carries an ordered chain of connectors, and live traffic goes to the first one whose credentials are present in the deployment you are calling.

Some connectors an operator can switch on alone in minutes — GoCardless Bank Account Data (UK and EU banks, free self-signup under their PSD2 licence), Coinbase, Kraken, PayPal, public-address crypto wallets, and CSV / OFX / QFX import. Others need a signed business relationship before they will serve production data, including Plaid, MX, Finicity, Akoya, and Stripe Financial Connections. Where an institution has no enabled connector, a live call returns provider_error rather than pretending.

The sandbox is the exception and it is always on: test keys resolve to the simulated network regardless of credentials, so the full integration is buildable on day one. See going live for the provider-by-provider breakdown.

// how to connect it

Two calls and one modal.

Passing institution_id opens Link directly on Mercari instead of the picker — useful when your own UI already asked which bank.

import { FeelConnect } from "@feelconnect/node";
const fc = new FeelConnect({
apiKey: process.env.FEELCONNECT_SECRET_KEY!,
baseUrl: "https://connect.feels.money/v1",
});
// Pin the flow to Mercari: Link opens straight on its auth step
// instead of the institution picker.
const { link_token } = await fc.link.createToken({
client_name: "Your app",
user: { client_user_id: "user-123" },
products: ["balances", "transactions", "recurring"],
institution_id: "inst_mercari",
});

The browser receives only the link_token, which expires in thirty minutes. Link runs the institution’s auth step, any MFA challenge, account selection, and the consent screen, then hands back a public_token. Exchange it once on your server with fc.link.exchangeToken and store the resulting access_token encrypted. Full walkthrough in the quickstart.

// in the api

Mercari as the API returns it.

The response below is generated from this institution's row, so it is the shape and the values a real call gets back.

# Look the institution up by id.
curl https://connect.feels.money/v1/institutions/get_by_id \
-H "Authorization: Bearer $FEELCONNECT_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{ "institution_id": "inst_mercari" }'

logo_url is a path on this origin rather than a third-party CDN, so rendering the mark never tells anyone else which institution your user is looking at. primary_color and monogram are the fallback tile for clients that would rather not load an image at all. Field by field in the institutions reference.

In the sandbox this institution connects today. Because it is flagged as an OAuth institution, Link runs the simulated consent hand-off rather than asking for a password. Either way the item comes back with 24 months of deterministic history — enough to build and demo the whole integration before any provider agreement exists. Sandbox reference.

// related

Institutions that route the same way.

Same category or same market — useful when you are checking coverage rather than one name.

  • PayPal Business logoPayPal BusinessUS
  • ADP logoADPUS
  • Amazon Seller Central logoAmazon Seller CentralUS · GB · DE
  • eBay logoeBayUS · GB · DE
  • Etsy logoEtsyUS · GB · CA
  • Paychex logoPaychexUS
  • Stripe logoStripeUS
  • Gusto logoGustoUS
  • Adyen logoAdyenNL · US · GB
  • Expensify logoExpensifyUS
  • Rippling logoRipplingUS
  • Payoneer logoPayoneerUS · GB

// keep reading

Where to go next.

  • All institutionsThe full catalog, grouped by type and country.
  • QuickstartKeys to synced transactions in about ten minutes.
  • Link referenceThe modal, update mode, and the postMessage protocol.
  • Going liveWhich providers are self-serve and which need an agreement.
  • PricingRequests, AI requests, connected users, and rate limits.
  • Bank data APIWhat you read once the connection exists.