A guide to evaluating compliance, liquidity, security and cost before you build your payments stack on someone elses rails

Imagine a founder who wants to add stablecoin payouts to a cross-border marketplace. The plan is simple: pay freelancers in minutes of days and avoid high wire fees. Then reality hits. The chosen provider changes its supported countries with two weeks’ notice. The launch stalls for three months.

This story happens all the time.. It doesn’t have to. Stablecoins are easy to understand.. Running them is hard. Behind every fast transfer is a network of issuers, custodians, banks, blockchains, compliance systems and liquidity sources. Your infrastructure provider decides how well that whole system holds up under stress.

Here’s a clear way to pick the one.

1. Start with your use case, not their feature list

Providers aren’t one-size-fits-all. Some focus on consumer apps others on business payouts or treasury tools. Before even seeing a demo write down:

• Which countries and currencies you must support\
• How transactions per month and how big they usually are
• Whether you need to accept deposits (on-ramps) send money out (off-ramps) or both
• Who controls the funds. You, your users or the provider

A clear use case stops you from wasting time on wrong options. It filters the market fast.

2. Ask about compliance and licensing

Regulation is now the difference between trustworthy providers and risky ones. New rules like the EU’s MiCA and the U.S.’s GENIUS Act require transparency, reserves and oversight. Don’t assume. Ask directly:

• What licenses do you. Where?
• Do you handle KYC, AML and transaction monitoring or do I?
• How do you follow the Travel Rule?
• Which stablecoins do you support? Are their issuers regulated?

Laws change. Check requirements with legal experts. If a provider answers these questions clearly and in writing they’ve likely done the work.

3. Look into security and custody

Stablecoin payments move money. They can’t be reversed. One mistake means loss. Look for:

• Independent audits like SOC 2 Type II
• Institutional-grade custody with customer funds kept
• Key management using multi-party computation or hardware security modules
• Role-based access and approval workflows for sensitive actions
• A public history of incidents and how they were handled

Security isn’t optional. It’s part of trust.

4. Test liquidity and settlement speed

Speed claims don’t mean much if the money isn’t available. A provider might promise transfers but large trades could face slippage or delays over weekends. Ask for numbers:

• Average and worst-case settlement times by corridor
• Which blockchains they support and what their gas fees look like
• When fiat rails operate. Including weekends and holidays
• Their uptime track record and whether they publish status updates

Real-world testing beats promises.

5. Look beyond the headline pricing

The price listed online rarely shows the cost. Compare cost of ownership not just percentages. Watch for:

• Spreads on currency conversion
• Whether network fees or gas costs get passed through
• monthly commitments or volume tiers
• Extra charges for onboarding, support or advanced compliance tools

Model the cost at today’s volume and at ten times that. Providers that seem cheap at volume often become expensive when you grow.

6. Judge the developer experience

Your engineers will work with this integration for years. A poor API slows sprints. Increases bugs. During evaluation let a developer spend a day in the sandbox. Then ask:

• Is documentation clear and complete?
• Are code samples helpful and accurate?
• Do webhooks fire and handle duplicates safely?
• Does the sandbox match production behavior?
• How quickly does technical support respond?

This isn’t about code. It’s about team pain.

7. Plan your exit before you sign

Vendor lock-in is a risk. Always ask: How would I leave if needed? Can I export transaction history and user data? Can I move wallets or balances to another custodian? Are contract terms fair? Good providers make leaving easier. Think about having a provider for backup once your volume grows. A single point of failure is a business risk. Not a tech issue.

Use a scoring framework

Turn the checklist into a weighted scorecard. Rate each shortlisted provider one to five in each category. Then assign weights based on what matters. A payments company may value compliance and liquidity at 30% each. A consumer app might care more about developer experience and cost. Share the scorecard with finance and engineering teams so everyone owns the decision.

Common mistakes to avoid

• Picking a provider based on price and discovering compliance problems later
• Skipping a live pilot before going full scale
• Assuming all stablecoins are equally safe or liquid
• Not knowing who takes responsibility when things break
• Treating the contract as a formality

Run a pilot before you commit

No research replaces actual testing. Run a pilot. Four to eight weeks. With clear goals. Process transactions across your key corridors. Track:

• Success rate on try
• Median and slowest settlement times
• How fast support responds during an incident
• Accuracy of reconciliation and reporting

Pay close attention to how the provider reacts when issues happen. A pilot always uncovers something.. Their response tells you more than any marketing material. Do they communicate early? Do they take ownership. Fix the root cause?. Do you have to chase them?

Questions to ask on the call

• What happens to customer funds if you go out of business?
• How do you notify users about outages or regulatory changes?
• Which banks support your fiat rails and how concentrated is that exposure?
• Can you give me references from customers with volume?

The bottom line

Choosing an infrastructure provider isn’t about finding the flashiest tool. It’s about finding a partner. The right one handles complexity keeps funds safe settles consistently and stays out of your way while you build. The wrong one becomes a bottleneck that your users feel long before you do.

Start with your use case. Verify compliance and security in writing. Test liquidity with transactions. Model costs at scale. Evaluate developers firsthand.. Always always plan your exit. Do these things. You’ll make a choice that stands up to your board, auditors and customers.

Disclaimer: This article is, for purposes only and does not constitute legal, financial or investment advice. Always consult professionals before making business decisions.

Choosing a Stablecoin Infrastructure Provider was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

Behind every ticker symbol is a crowd of banks, custodians and trading desks most investors never think about

Remember when buying Bitcoin meant a trip down a rabbit hole? Exchange signup, ID photos, a hardware wallet that arrives in the mail, and a 24-word phrase you’re told to write on paper and hide somewhere. Mess up any step and nobody is coming to help.

Then January 10, 2024 arrived. The SEC approved the first eleven spot Bitcoin ETFs, and all that hassle became optional. You could type a ticker into the same app where you hold your index funds and be done in thirty seconds.

Simple on the surface. Underneath, it’s a surprisingly busy machine. Let’s open the hood. I’ll keep the jargon light and the opinions honest, because this topic attracts plenty of hype in both directions.

First, what is a spot Bitcoin ETF?

It’s a fund that owns real Bitcoin and sells shares against it. The share price tracks Bitcoin, minus an annual fee. That’s it.

The “spot” part matters. Back in October 2021 the first Bitcoin ETFs launched, but they held futures contracts, and futures have to be swapped out every month. That rollover quietly eats returns, so those funds lagged the actual coin. Spot funds skip the problem.

The SEC said no to spot funds for about a decade. Its main worry was manipulation on crypto exchanges. Then a federal appeals court ruled in 2023 that the agency couldn’t approve futures funds while rejecting nearly identical spot ones. Awkward for the regulator, and the dam cracked soon after.

What you get as a buyer:

• Trading during normal market hours
• Compatibility with IRAs and brokerage accounts
• No keys or wallets to babysit
• Regular SEC filings, so holdings are public

The cast of characters

Nobody tells you how many companies touch a single share of IBIT. Here’s the short list.

• Issuers package the fund. Eleven launched together, among them BlackRock (IBIT), Fidelity (FBTC), Bitwise, ARK 21Shares, VanEck and Grayscale.
• Custodians store the Bitcoin, mostly in offline vaults. Coinbase handles a huge share of it. Fidelity keeps its own.
• Authorized participants are the big firms allowed to create or cancel shares in bulk.
• Market makers quote prices nonstop so you can buy or sell at a fair number.
• Pricing providers publish the benchmark rates that value each fund every day.
• The SEC watches over all of it.

Honestly, the authorized participants and market makers are the least famous and most important group here. Without them, the ETF price would wander.

The clever bit: creating shares

Picture the ETF trading a little above its Bitcoin’s value because everyone wants in. Here’s what happens next.

1. An authorized participant notices the gap.
2. They hand the issuer cash (since 2025, Bitcoin itself also works).
3. The issuer makes new shares, and the custodian ends up with matching coins.
4. Extra shares hit the market, and the price sinks back to fair value.

Demand falls? Same thing in reverse. Shares get cancelled and Bitcoin goes back out.

This loop is why a healthy ETF almost never strays far from its holdings. When you do spot a big premium or discount, something is stressed.

Fees, flows and one big winner

Issuers went to war over price. Most settled between 0.2% and 0.3% a year, and a few waived fees entirely for a while. BlackRock offered a temporary discount on IBIT. Fidelity waived FBTC’s fee for the early months.

Grayscale was the odd one out. Its old trust, GBTC, was converting into an ETF and charged 1.5%, which looked silly next to everyone else. Money poured out for months, since holders stuck in the old structure finally had a cheaper exit.

Meanwhile IBIT raced ahead, collecting tens of billions faster than almost any ETF in history. The lesson: when products are nearly identical, people pick the name they trust and the lower price.

Why this matters

• Easier entry. Millions of people who’d never open a crypto exchange account now hold Bitcoin exposure.
• Respectability. Advisors and institutions finally have something their compliance teams can sign off on.
• Transparency. Holdings and flows get reported, so there’s real data to argue about.
• A ripple effect. Spot Ether ETFs, options on Bitcoin ETFs and looser listing rules for other crypto funds all followed.

Whether Bitcoin deserves a place in portfolios is a separate debate. The ETFs just made it easy to join that debate with real money.

What can go wrong

Easy doesn’t mean safe. Think about these before buying.

• Wild swings. A 10% move in a week isn’t unusual, and your ETF follows.
• You don’t own coins. You own shares. No withdrawals, no using it for payments or apps.
• Concentrated custody. A handful of custodians hold most of the Bitcoin. One serious failure could ripple across funds.
• Fees add up. Small percentages become real money over a decade.
• Taxes. Rules differ by country and account type, so look yours up.
• Weekend gaps. Bitcoin never sleeps, but the stock market does. Big news on Saturday waits until Monday for your ETF to react.

ETF or self-custody?

Neither is “right.” It depends on what you want.

If you want simplicity, retirement-account access and a regulated structure, the ETF fits. If you want full control, the ability to move coins anywhere and round-the-clock access, hold your own. A lot of people split the difference, and honestly that seems sensible.

Where this goes next

Keep an eye on a few things:

• Advisors adding Bitcoin to standard model portfolios
• More crypto ETFs beyond Bitcoin and Ether
• Rule changes around staking and custody
• Fees dropping further

The takeaway

Crypto invented the asset. Wall Street built the on-ramp. The result is a market where your neighbor can own Bitcoin without knowing what a private key is, and that’s both the whole point and the whole risk.

My advice, for what it’s worth: understand what’s inside the ticker, compare expense ratios, and don’t put in more than you can stomach losing. Bitcoin has humbled plenty of confident people, and an ETF wrapper won’t change its temperament.

So which camp are you in, ETF or your own wallet? I’d like to hear why in the comments.

Bitcoin ETFs Explained: Who Actually Runs This Thing? was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

Three payment models that look identical on a slide deck and feel nothing alike in real life

A founder I’ll call Dev launches a small booking app for salons. In week one, a customer pays for a haircut. Dev checks his dashboard, sees the money, and assumes payments are basically solved.

Then a chargeback arrives. Then a compliance email. Then a question from his payment provider that he can’t answer: who, exactly, is responsible here?

That question is why this article exists. ISO, PayFac and acquirer get tossed around like synonyms. They aren’t. Pick the wrong one and you’ll find out at the worst possible time.

Four players and a referee

Strip away the jargon and every card payment involves the same cast:

• Cardholder: the person tapping their card
• Merchant: the business getting paid
• Issuer: the bank that gave the customer the card
• Acquirer: the bank on the merchant’s side
• Networks: Visa and Mastercard, who write the rules

ISOs and PayFacs squeeze in on the merchant side. What separates them is who holds the license, who absorbs losses, and who owns the customer.

The acquirer: holder of the keys

An acquirer is a licensed bank with direct membership in the card networks. It vets merchants, settles funds, and takes the fall when things break. If a merchant disappears owing thousands in chargebacks, the acquirer gets the call.

Going direct gets you the cheapest rates, but only at serious volume. Getting there means capital requirements, PCI DSS audits, and onboarding that can take weeks. Most small businesses never talk to one. Honestly, most wouldn’t enjoy it.

The ISO: the salesperson

An Independent Sales Organization resells an acquirer’s services. It finds merchants, signs them up, and collects a slice of their processing fees for as long as they stay. It doesn’t hold funds and has no license of its own.

In practice that means:

• Each merchant signs its own account with the acquirer
• Every business is underwritten individually
• Support is personal, often local, and often includes terminals
• You get little say over pricing, tech, or payout speed

This suits restaurants, clinics and corner shops, where a person answering the phone beats a well-documented API. Unglamorous. Effective.

The PayFac: the platform play

A payment facilitator is a merchant of record that brings many small sellers under one master merchant account. Stripe and Square made the model famous. Instead of forms and a two-week wait, a PayFac can approve a seller in minutes using automated checks.

The price of that speed is responsibility. Fraud, chargebacks and sub-merchant compliance land on the PayFac first, and the acquirer holds it accountable. What you get back: control over checkout, pricing and payout timing, plus the customer data. For a software company, that’s the prize.

A mall, because analogies help

Think of a shopping mall. The acquirer owns the building and writes the lease rules. The ISO is the leasing agent who finds tenants and takes a commission. The PayFac is a master tenant who sublets small stalls to dozens of vendors, sets their terms, and answers to the owner when one of them causes trouble.

Side by side

• Licensing: the acquirer has full membership, the ISO borrows it, the PayFac operates under sponsorship
• Speed: acquirers are slow, ISOs moderate, PayFacs nearly instant
• Risk: acquirers carry the final liability, PayFacs carry sub-merchant risk, ISOs carry the least
• Best fit: enterprises, traditional shops, software platforms

Who makes money, and how

Every payment has layers: interchange to the issuer, network fees, then a markup on top. Who keeps that markup depends on the model.

• Acquirers earn thin margins on enormous volume
• ISOs earn residuals, a monthly share of each merchant’s fees, plus equipment sales
• PayFacs keep the spread between the wholesale rate they pay and the flat rate they charge

That spread explains why so many software companies want in. Payments can turn a subscription product into a second business.

So which one do you pick?

There’s no universal answer, but there are patterns.

• Choose an ISO if you run a traditional business and want a quick start, real human support, and hardware included.
• Become a PayFac if you run a platform or marketplace and want smooth onboarding, branded checkout, and payments revenue.
• Go direct to an acquirer if your volume is huge and your team can handle risk, compliance and integration alone.

Where people trip up

The same mistakes keep showing up, and most are avoidable:

• Underestimating compliance. PayFacs deal with PCI DSS, KYC and constant monitoring. None of it is optional.
• Shrugging off chargebacks. Disputes hit the PayFac first, and a high ratio can end the acquirer relationship overnight.
• Skimming the contract. ISO agreements sometimes hide early termination fees and long lock-ins.
• Building too soon. Full PayFac status costs real money, and plenty of startups aren’t ready.

The middle path

Which brings us back to Dev. He doesn’t need to become a PayFac yet. He needs PayFac-as-a-Service: PayFac-style onboarding while a partner handles underwriting, compliance and risk.

He launches faster, keeps a good chunk of the revenue, and can graduate to full PayFac status once volume justifies the bill.

Questions to ask before you sign

Before committing to anything, sit down with these:

• How many merchants will you onboard, and how fast?
• Do you need control over checkout and payouts?
• Can your team realistically handle fraud and compliance?
• Is payments revenue central to your plan, or a bonus?
• What’s your budget and launch timeline?

Where this is heading

The boundaries are blurring. Big acquirers now sell embedded payments, ISOs are bolting on software, and PayFacs are chasing direct bank relationships. Card networks keep tightening sub-merchant onboarding rules too, so strong risk controls matter more every year.

Bottom line

These three aren’t rivals so much as layers of one stack. The acquirer builds the rails, the ISO sells access, and the PayFac wraps it all into something people actually enjoy using.

Match the model to your stage. New and small? Keep it simple. Payments central to revenue? Push for control. Massive volume? Talk to an acquirer directly. Get that call right early and payments stop being a headache.

ISO vs PayFac vs Acquirer: Who Actually Gets Paid When You Swipe? was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.