←
Fystack1,021 posts
Fystack avatar

Fystack

@fystack

Automate your stablecoin stack: wallets, payments and payouts, on one open platform.

◷ Joined March 2025▧ 342 Photos and videos
Fystack avatar
Fystack@fystack·Aug 19

Last week, @fystack joined Hack Seasons Conference Ho Chi Minh City as a sponsor, alongside @securosys, @Ledger, @SonicLabs, @birdeye_so , @Mercuryo_io and others. What stood out throughout the day was how naturally conversations moved between traditional finance and digital assets. We had the chance to speak with banks, payment companies and exchanges about where the industry is heading, from stablecoins and institutional adoption to custody, compliance and security. One thing was clear: the conversation is becoming much more practical. It's no longer just about whether institutions are interested in digital assets, but how they can actually operate them securely and compliantly. Thanks to @mpost_io team for the support throughout the event!

Post attachmentPost attachmentPost attachment
Fystack avatar
Fystack@fystack·7h

As digital asset operations scale, more people, wallets and API keys can move your funds. That’s why we built Fystack v0.4.0: to help you control who approves each transaction, spot unusual API key activity early, and see every action in one place. Here’s what’s new: → Approve from your phone: pair your phone as a cosigner on an MPC wallet, and every transaction from that wallet also needs your approval in the Fystack Cosigner app → Set rules by user, API key, wallet or destination, and cap 24-hour outflow → Get an email and a webhook when an API key acts unusually, from a new country, a new IP or after being dormant. Rotate or revoke it in one click → See every action in your workspace in one audit log, and export it to CSV → Create many HD-MPC child wallets from one master wallet, and use them as sweep sources We also made accounts harder to take over: idle sessions sign out after 15 minutes, policy approvals require MFA, API key changes require 2FA, and replayed API requests are blocked. Full release notes: docs.fystack.io/changelog/v0…

Post attachment
Fystack avatar
Fystack@fystack·Nov 17

Many fintech and payment teams still run on single-party custody: one provider, one key holder, one signing server. When that party is compromised, through a hack, an insider, or a stolen device, the funds go with it. That’s the risk we built Fystack Cosigner to remove. It’s now open for early access. → No single party can sign alone: transactions need 2-of-3 or 3-of-3 approval → Spread signing across your servers, mobile devices, and team members → Export your key share and recover your wallet yourself, without depending on Fystack Server Cosigner and Mobile Cosigner are both running in production. Android is live, iOS is coming soon. Our CLI and recovery tools are open source, so you can inspect how they work. We're onboarding a limited number of teams first. Join the Beta whitelist: link.fystack.io/cosigner.

1:16
Fystack avatar
Fystack@fystack·Nov 16

What if an employee's laptop gets hacked? With Fystack, access to one device does not mean access to company funds. Fystack protects digital assets with multiple layers of security: → Passkey & 2FA add extra checks when users log in. → Role-based permissions control what each team member can do. → MPC signing splits the private key into separate shares across multiple nodes. No single node holds the full key. → Approval Groups require multiple team members to approve a transaction. → Transaction Policies check each transaction against company rules. They can block transfers that exceed set limits or go to unapproved addresses. Even if a hacker gets into one device, they cannot move funds without passing the other security checks. One hacked laptop shouldn't put company funds at risk. That's how Fystack protects digital assets.

0:58
Fystack avatar
Fystack@fystack·Nov 13

🌍 Fystack docs now speak Spanish and Chinese Many of our clients asked for it, and now it’s live. The Fystack documentation is available in Spanish 🇪🇸 and Chinese 🇨🇳, alongside English. Our goal is to make it easier for teams everywhere to build with Fystack, whatever language they work in.

0:14
Fystack avatar
Fystack@fystack·Nov 13

10,000 users. 10,000 deposits. How do you manage them all? As your crypto app grows, managing wallets becomes an operational challenge. You need to: - Create and manage deposit addresses. - Track incoming transactions. - Monitor balances across wallets. - Consolidate funds without manual transfers. This is where wallet infrastructure matters. Fystack helps fintechs and payment companies manage wallets, monitor transactions, and automate fund sweeping as they scale. Build your product. Let Fystack handle the wallet infrastructure. Explore our docs: docs.fystack.io/

0:58
Fystack avatar
Fystack@fystack·Nov 10

Adding a new blockchain is more than an API integration. The real work starts when you need to handle different address formats, signing schemes, fee tokens, deposit rules and transaction finality. Even the same USDC can behave differently across chains. We put together a 12-point checklist to help payment and fintech teams prepare for a new network, covering keys, connectivity, money mechanics and operational controls. Read the full guide: fystack.io/blog/multi-chain-…

Post attachment
Fystack avatar
Fystack@fystack·Nov 10

It's our pleasure to see our founder, @thicody, featured in Rise In's Builder Spotlight! Thi shared his startup journey with the Stellar community, including why he started Fystack and how we're building a wallet that never holds the whole key. Thanks to @riseinweb3 for featuring his story! Read the full story 👇 risein.com/blog/builder-spot…

Fystack avatar
Fystack@fystack·Nov 5

We’re proud to share that Fystack is now ISO/IEC 27001:2022 certified, the international standard for information security management. An independent auditor reviewed how we protect our systems and our customers’ data. Security is built into every layer: - Applications: secure development practices, code review and continuous testing. - Dependencies: we monitor third-party libraries and patch known vulnerabilities quickly. - Cloud and containers: hardened infrastructure, least-privilege access, and isolated workloads. - Internal access: our team works on a zero-trust network and signs in with hardware security keys. Private keys are never held in one place, thanks to our MPC wallet design. Our MPC engine is open source: github.com/fystack/mpcium Security isn’t a one-time milestone. It’s a commitment we renew every day. See all our security controls on our Trust Center: trust.fystack.io Thank you to our team and partners for helping us get here!

Post attachment
Fystack avatar
Fystack@fystack·Nov 5

3. OTC desks and B2B settlement Businesses moving larger amounts across borders need reliable ways to trade, convert and settle stablecoins. This creates opportunities for fintechs offering OTC services and B2B payment infrastructure.

Fystack avatar
Fystack@fystack·Nov 5

2. Merchant stablecoin payment gateways Merchants need ways to accept payments from international customers without relying entirely on traditional cross-border payment rails. Fintechs can build gateways that help businesses collect stablecoins and track incoming payments.

Fystack avatar
Fystack@fystack·Nov 5

1. Stablecoin off-ramps to mobile money Users may hold USDT or USDC, but still need local currency for everyday payments. Fintechs can bridge this gap by converting stablecoins into local currency and paying out through mobile money or bank transfers.

Fystack avatar
Fystack@fystack·Nov 5

Stablecoin adoption is creating new business opportunities across Africa. Here are 3 business models worth exploring 🧵

Post attachment
Fystack avatar
Fystack@fystack·Nov 4

Having MPC is not enough. You also need to control what gets signed. Binance’s $6.3B hack shows why. Binance found no evidence of a private key leak. Its Nov 3 report traces how attackers moved from a fake job interview to compromised engineer devices, then to the wallet signing system. MPC protects the key by splitting the signing process, so no single machine holds the full key. It does not decide whether a transaction should be signed. That takes more layers: • MPC: protects key management and signing • Access control: who can act • Transaction policies: which transfers are allowed • Approval workflows: who must sign off, and when • Monitoring: what looks wrong, in real time Assume a laptop will be compromised. Build so it can’t reach what signs. At @fystack, policies run before signing, not after.