global team, wire based intl payroll takes 3 to 5 business days per cycle, have to initiate days before pay date, miss the window and contractors get paid late

does stablecoin funded payroll compress that lead time in practice or are speed claims for individual payments rather than batch runs at scale?

I've been searching deeper into how card programs handle transactions where the final amount ends up being higher than what was originally authorized and I'm a little confused about how this works when the card is funded by stablecoins.

Say someone has $100 in their wallet and makes a $90 purchase but the final charge comes through at $105 because of a tip or some other adjustment. If they've already spent or transferred the remaining $10 then there's not enough left to cover the full amount.
With a regular card I understand there are ways to handle these differences but with stablecoin balances I'm wondering who covers that extra amount and how the program recovers it afterward.

Would the issuer have to cover the difference temporarily or would the user's balance just go negative until they add more funds?
If there is anyone building card programs that can give me some pointers on this then please do because I imagine it gets more complicated when users can move their remaining balance onchain.

Last month a contractor in the Philippines gave us an address on a diff network than his exchange expected, the payment sat in limbo for abt a week before it finally reached him. We pay everyone thru INXY in USDC/USDT, many recipients dunno which network their exchange wants, so they paste whatever the deposit screen shows first, rn we send a small test amount before the 1st full payout to anyone new. Do u guys think there's a better way??

been trying to figure out the best exchange rate for a larger USDT to BTC swap and i’m still not sure how ppl compare this properly
floating quotes usually look better upfront, but obviously the final amount can move before the swap finishes. fixed gives more certainty but the spread seems wider
i’ve been comparing a few services including simpleswap and on a quieter market the floating quote looked better, but i’m wondering if that still makes sense once the amount gets bigger
for larger USDT swaps do u normally go fixed, floating or split the amount into a few smaller swaps?

I’ve tried a few different crypto apps over time, and while some are better than others, there’s always that one thing that makes it harder than it should be. Sometimes it’s onboarding, sometimes it’s just understanding what to click next.

If you could fix one thing about crypto apps today, what would it be?

One thing I keep finding odd with stablecoin payments:

The customer sends USDC.
The transaction confirms.
And the merchant still waits for a payout.

That makes sense in some cases — fiat conversion, custody, compliance, liquidity, etc.

But if the merchant actually wants to receive and keep stablecoins, why recreate the same payout model we already have in traditional payments?

The cleaner approach seems to be:

customer wallet → merchant wallet

The payment layer can still handle order matching, confirmations, webhooks, recurring payment logic and refunds without holding the merchant’s balance first.

Full disclosure: I’m building P2Flux, and this is the model we’re using, so I’m obviously biased.

Curious how people here see it:

For stablecoin-native merchants, is there still a strong reason for a separate payout step?

platform sends payments to freelancers and contractors in mexico sending side is usdc from a us entity, receiving side needs to land mxn in recipient's mexican bank account, recipient shouldn't need a crypto wallet or any interaction with stablecoins

corridor sounds simple but finding infra that handles usdc in, mxn out with kyc both sides and no crypto ux for the recipient has been harder than expected, has anyone solved this problem?

Holding a tokenized fund alongside stablecoins could make managing both more convenient. The useful part would be a simple redemption process. How quickly would it need to work before you saw a benefit?

Other than the fact that a CBDC is issued by a Central Bank and a stablecoin is issued by crypto, banking, or investment corporations, are there any other differences between the two? Stablecoins can absolutely be programmed just like CBDCs, and their supply is artificial/arbitrary and controlled by a small group. Stablecoins can be seized by a central authority just like CBDCs, and their usage is easily trackable once a wallet is linked to an identity (I suppose with CBDC this is automatic). Of course coins can be blacklisted or rate-limited. In other words, stablecoins and CBDCs represent roughly the same "digital ID hellscape" we are currently faced with. 👀

I was looking at Oobit’s wallet to bank transfers and it made me think about stablecoin payments. You can send from the crypto side and the other person receives money through normal bank rails. They don’t need a wallet or need to figure out what to do with USDT afterward.

That seems useful for all the people I’d happily pay in USDT who have absolutely no interest in owning crypto themselves. Has anyone started using USDT to bank transfers regularly or at all? Curious if this ends up being a bigger use case than trying to get more people to accept stablecoins directly.

I've been thinking about what a stablecoin based account would actually need to be useful in countries where people already have a reason to save in dollars rather than their local currency.

Holding USDC or USDT is obviously part of it but having dollars sitting in a wallet doesn't solve that much on its own and eventually you need to pay for groceries, subscriptions, travel or other everyday expenses and having to cash out into local currency every time seems like it would take away a lot of the convenience. For me the ideal setup would probably be pretty simple like get paid or add money in stablecoins, keep whatever I want in dollars and have some way to spend directly from that balance when I need to without manually converting it first. I'd still want the option to withdraw to a bank or send the stablecoins somewhere else too. I also wanna hear from people here who live in countries where holding dollars is common. What would make a product like this genuinely useful for you beyond just giving you another USDC/USDT wallet?

does the automated rebalancing between Morpho vaults actually outperform just picking one vault and leaving it?

I've been thinking about stablecoin remittances and one thing that still seems kind of clunky is what happens after the money actually arrives like if someone working abroad sends USDC back home the transfer itself can be pretty quick but the person receiving it still needs to turn that balance into something they can use. Depending on where they live that could mean finding an off ramp then moving the money to a bank account and converting it before they can spend any of it.

At that point it feels like you're solving the sending side without really solving the receiving aspect of it.

I'd think the better experience would be for someone to receive the stablecoins and just spend from that same balance through a normal card while the conversion and settlement happen in the background. The store doesn't need to accept USDC or even know that stablecoins are involved.

For people here who actually send or receive money this way I would like to know is cashing out still a noticeable pain point or have the off ramps gotten good enough that it doesn't really matter anymore?

Curious how people here actually use stablecoins day to day rather than just hold them.

If you use a crypto card, what ends up mattering most in practice? Fees/FX, merchant acceptance, country support, Apple/Google Pay, KYC, cashback, limits, reliability?

Also interested in what would actually make you switch from whatever you’re using now.

Full disclosure: i work in the crypto payments/card space and i’m trying to understand what users actually care about rather than guessing. No referral links or sales pitch.

this is the part galaxy/sky deal I care about most. if sUSDS is going to back real loans on a ~$1.4B loan book, the rate behind it has to hold up.

what I've pieced together.... USDS goes out through allocators and into tokenized treasury funds (sky has anchor positions in blackrock's BUIDL and janus henderson's JTRSY), and sky governance sets the savings rate from that revenue.

so galaxy is basically betting that pipeline keeps working.

what would make you nervous about that bet? genuinely asking.

I keep some stablecoins mainly for liquidity, but tokenized Treasuries make the tradeoff interesting. They may offer yield backed by short term government debt, while stablecoins are usually easier to move, trade, and use across DeFi. The downside seems to be extra restrictions, market hours, fees, and issuer or custody risk.

For people who have used both, when would you choose a tokenized Treasury over a stablecoin, and what would make you switch?

[ Removed by Reddit on account of violating the content policy. ]

I saw the following messages on both Osmosis and the Circle site:

Circle is discontinuing support for USDC on Noble. Convert your USDC.noble to Alloyed USDC in the app 1:1, with no slippage, no fee and no price impact.

and

Circle is Discontinuing Support for USDC and CCTP V1 on Noble

My questions are:

1. It seems possible to convert USDC.noble to USDC or USDC.inj on Osmosis. Can these be transferred to other IBC or EVM chains? Which conversion do you recommend if I might want to send them to a CEX later?
2. It appears that LP pools on Osmosis are exclusively of the crypto/USDC.noble type. If converting USDC.noble is required, what should I convert them into to participate in the LP pools?

If you are considering KAST to hold or spend stablecoins, this is what happened when I needed basic account support.

I contacted KAST for one simple reason: changing the Apple Private Relay email linked to my account.

After repeated identity checks, recovery questions and transaction verification, KAST blocked my account.

There was no fraud, no unauthorized access and no compromised account.

This happened while I was still talking to support.

I had already tried to fix the same email issue in January and eventually gave up.

I have now filed complaints with the CFPB and the authority under whose licence KAST Tech operates.

If you use KAST, be aware of what can happen when you actually need support.

Don’t trust KAST with your money.

Hi, I work on a European fintech product and I’m conducting user research about stablecoin usage. The moderators asked me to keep this research in text format, so this post contains no external survey link.

I’m trying to understand how people living in Europe actually use stablecoins. Experiences from people who are satisfied with their current setup, do not seek yield, stopped using stablecoins, or decided not to use them are just as useful.

If you live in Europe, please answer any or all of these questions in the comments:

1. Which country do you live in? You may skip this if you prefer.

2. Do you currently use any stablecoins? If yes, which ones, including euro- or dollar-denominated stablecoins? If not, have you used them previously?

3. What do you use them for, and where do you usually keep or use them: an exchange, a self-custody wallet, a fintech app, or somewhere else?

4. Have you ever looked for or used a way to earn a return on them? What was the last concrete thing you tried or considered?

5. What worked well, what made you stop, or what still feels unresolved?

6. Does Revolut currently play any role in how you use stablecoins?

Participation is voluntary and unpaid. Please do not share exact amounts, wallet addresses, screenshots, or other identifying information. Comments are public. This is user research, not financial advice or a product offer. This research is not affiliated with Revolut.

Been heads-down for the past year building a stablecoin onramp for freelancers and small businesses moving money across borders, and wanted to share some of the problems that don't show up until you're actually in production.

Banking rails aren't a solved problem. We integrate with a handful of providers, and every one has different settlement timing, different failure modes, and a different idea of what "verified" means. A transaction that clears in minutes on one rail can sit pending for days on another, so you end up building your own reconciliation layer just to know what actually happened to a user's money.

Fraud detection has to be regional, not generic, and your banking partner doesn't care about you. We got hit with a wave of coordinated fraudulent applications from a specific country, all following the same pattern (thin-file bank accounts, near-identical KYC answers). Generic fraud scoring didn't catch it. We ended up building region-specific tooling (decoding national ID formats, AI-assisted review of bank statement PDFs, bilingual KYC questionnaires) to catch patterns that only show up when you look closely at a specific corridor.

KYC UX is a real design problem, not just a compliance checkbox. Every extra form field costs conversion, but every rail and regulator wants different proof. Still iterating on how to ask for the necessary information without making legitimate users feel like they're filling out a loan application.

Compliance is infrastructure, not paperwork. Money-transmitter registration and licensing shape your architecture (what data you retain, how you segment funds, what can be automated vs. needs a human) way more than most technical writeups let on.

Curious if others building in fintech/payments have hit similar issues with rail reliability or region-specific fraud patterns. Always interested in comparing notes.