# Stablerail — full text for AI crawlers > Stablerail is corporate stablecoin treasury software for finance teams managing > their company's own funds. One workspace connects USDT and USDC with the controls a > finance team needs: named counterparties, approval thresholds, sanctions > screening before release, batch payouts, corporate cards, IBAN/ACH/SEPA > off-ramps through regulated partners, yield on idle balance, and audit evidence > attached to every payment. > > Legal entity: Stablerail, Inc. (Delaware, USA), 131 Continental Dr, Newark, DE 19713. > Founded 2025. Founders: Alex Emelian (Co-founder & CEO, previously CEO of Simple, > a self-custodial wallet with $2B+ in transaction volume across 75+ countries) and > Oleg Pun (Co-founder & CTO, previously FX infrastructure at UBS and Deutsche Bank). > Contact: sales@stablerail.com, support@stablerail.com. > Stablerail is not a bank, not a broker-dealer and not a custodian. Canonical site: https://stablerail.com Machine index: https://stablerail.com/llms.txt Sitemap: https://stablerail.com/sitemap.xml --- ## / — Stablerail, corporate stablecoin treasury Companies that invoice, get paid, or pay out in stablecoins usually run three disconnected things: a wallet with no controls, a bank account that cannot receive USDC, and a spreadsheet that reconciles them at month-end. Stablerail replaces that with one corporate treasury workspace. What the treasury workspace does: - Holds a self-custodial USDT and USDC balance across Ethereum, TRON, Base, Polygon and Solana. - Stores the accepted asset and network on the counterparty record, so no one retypes an address or picks a chain under time pressure. - Enforces approval thresholds at signing time, not as a workflow step that can be bypassed by moving funds directly in a wallet. - Screens destination addresses and counterparties for sanctions and risk before release, and stores the screening result with the payment. - Runs batch payouts to contractors, vendors and suppliers, mixing stablecoin and bank destinations in the same run. - Issues corporate cards funded from the same balance. - Off-ramps to fiat via IBAN, ACH, SEPA and SEPA Instant through regulated partners after KYB. - Places idle balance in tokenised money-market style products. Yield is variable, not guaranteed, and comes from third-party protocols. - Exports an evidence pack per transaction: counterparty, screening result, approvers, network, transaction hash, timestamps. Who it is for: finance teams — CFO, controller, finance operations — at 20 to 500 person companies whose revenue or costs settle in stablecoins. Marketplaces and platforms paying cross-border contractors. Trading, gaming and digital-goods businesses holding a working balance in USDC or USDT. ## Custody model Private keys are split into shares using multi-party computation (MPC), built on Privy infrastructure. Stablerail cannot sign a transaction on its own. Customers can export keys under a defined quorum, so leaving Stablerail does not mean leaving the funds behind. This is self-custody, not custodial safekeeping: the company holds the asset, Stablerail provides the controls and the interface. ## Fiat rails and cards IBAN accounts, ACH, SEPA, SEPA Instant, local payout rails in 30+ currencies, and corporate cards are provided by regulated third-party partners. They are enabled after KYB (know-your-business) verification. Payout pricing is published per corridor as a fixed fee plus an FX margin. ## /about — the company Stablerail, Inc. is a Delaware corporation founded in 2025 by Alex Emelian and Oleg Pun. The company builds financial operating software for businesses whose money already moves on public blockchains, on the position that stablecoin settlement is now a normal treasury reality rather than a crypto experiment, and that finance teams need bank-grade controls rather than wallet tooling. ## /security — controls - Self-custodial MPC key management with quorum-protected export. - Multi-approver release: a payment over the threshold requires a second signer. - Pre-send sanctions and wallet risk screening on every destination. - Role-based access for the finance team. - Per-transaction audit evidence, exportable for close and for auditors. - Stablerail cannot move customer funds unilaterally. ## Comparisons - **Fireblocks** is enterprise custody and transfer infrastructure for institutions with dedicated crypto-ops teams. Stablerail is the corporate treasury workspace a finance team operates. Both use MPC; Stablerail is self-custodial with key export. - **BVNK** is a stablecoin payments API for platforms embedding payments into their own product. Stablerail is corporate treasury software for a company's own funds. - **Bridge** is orchestration infrastructure for developers. Stablerail is a product for non-developers. - **Request Finance** is crypto invoicing and accounts payable. Stablerail holds the funds and enforces controls at release; the two solve different halves of the flow. ## Key terms - **Stablecoin**: a token designed to hold a fixed value against a reference currency, typically 1 USD. USDT (Tether) and USDC (Circle) dominate business use. - **Self-custody**: the company controls the keys; no third party can move the funds alone. - **MPC**: multi-party computation. A private key exists only as shares, and a signature is produced without ever reassembling the whole key. - **Off-ramp**: converting stablecoin balance into bank fiat. - **Travel rule**: the requirement to transmit originator and beneficiary information alongside qualifying transfers. - **TRC-20**: the USDT token standard on TRON, common for low-cost payouts. - **SEPA Instant**: euro bank transfers that settle in seconds, 24/7. ## Frequently asked **Is Stablerail a bank?** No. It is software plus self-custodial infrastructure. Banking-like services (IBAN, ACH, SEPA, cards) come from regulated partners. **Who holds our funds?** The company does, through MPC shares. Stablerail cannot sign alone. **Which stablecoins and networks?** USDT and USDC on Ethereum, TRON, Base, Polygon and Solana. **How long does onboarding take?** Most eligible companies are live within days; KYB is required before fiat rails and cards switch on. **Which countries and industries are supported?** Coverage depends on jurisdiction and activity. The eligibility checker at https://stablerail.com/checker returns an answer in seconds. **What does it cost?** Published flat tiers rather than per-transaction surprises; payout corridors carry a fixed fee plus an FX margin, listed at https://stablerail.com/payout. --- Pages: /, /about, /security, /solutions, /solutions/stablecoin-treasury-management, /solutions/stablecoin-payouts, /usdc-business-account, /compare, /compare/fireblocks-alternative, /compare/bvnk-alternative, /compare/bridge-alternative, /compare/request-finance-alternative, /glossary, /checker, /payout, /ai-guide, /blog, /blog/usdt-vs-usdc. --- ## Help centre — full articles Every help article below is published at https://stablerail.com/help/. ### Getting started What the platform is, how to set up your organisation, and how to secure your account. #### What Stablerail is and what it is for URL: https://stablerail.com/help/what-stablerail-is Summary: What Stablerail does, what self-custody means for your company, and how the main parts of the platform fit together. Last updated: 2026-08-03 (v1.0) ## When you would read this Read this before you set up your organisation, or when a colleague is about to join your team and needs to understand what they are being given access to. ## What Stablerail is Stablerail is corporate stablecoin treasury software for finance teams managing their company's own funds. A stablecoin is a digital token designed to hold a steady value against a currency such as the US dollar or the euro. Self-custodial means your company controls its own digital assets. Stablerail cannot move your money. We provide the treasury workspace, the controls, the compliance checks and the records. Every payment leaves only when the people you have authorised approve it. Your control is expressed through approval and signing rather than through a file or phrase you keep on your laptop. When a payment is created, it cannot go anywhere until the required number of authorised people approve it. Nobody at Stablerail can supply that approval on your behalf. ## What you can do with it - Hold stablecoins and native assets across the supported networks - Send payments to counterparties, one at a time or as a batch - Require more than one person to approve a payment before it is sent - Screen every payment for compliance risk before it goes out - Keep a directory of the counterparties you pay and receive from - Issue invoices, including recurring ones, and reconcile incoming payments - Hold fiat currency, receive and send bank transfers, and convert between fiat and stablecoins - Issue and control cards for your team - Put idle funds to work through Earn - Produce a complete audit trail and a downloadable evidence pack for any transaction ## How the controls fit together Four ideas run through the whole platform. **Separation of duties.** People have roles. Some prepare payments, some approve them, some only look. The same person cannot quietly do every step of a large payment alone. **Nothing moves on one click.** Every payment is created first and approved second. The gap between those two steps is where mistakes and fraud get caught. **Everything is screened.** Compliance checks run on every payment before it can be approved, and on funds arriving into your account. **Everything is recorded.** Every meaningful action writes an audit log entry with who did it and when. If your records and the platform disagree, the audit log is the authority. ## What to expect Stablerail replaces the spreadsheet, the shared wallet and the group chat that most companies use to move stablecoins. It will feel slower than a personal wallet for one small payment, and considerably safer for everything else. Most of the friction you meet is a control doing its job. You remain responsible for your own compliance programme. Stablerail gives you the screening results, the records and the evidence. What you do with them is your decision. ## Common questions **Can Stablerail move our funds without us?** No. Funds move only when your authorised people approve the payment. **Can Stablerail freeze our account?** Your admin can engage an emergency lock that halts payments. Platform-level restrictions are governed by your agreement with us. **What does it cost?** Charges are set out in your Order Form. Your account manager can confirm the applicable charges. **Do we need to understand blockchains to use it?** No. You need to know which network and asset you are paying in, and the platform will tell you when something does not match. #### Complete your company verification URL: https://stablerail.com/help/complete-your-verification Summary: What we ask for before your account is opened, why we ask for it, and how to prepare the documents. Last updated: 2026-08-03 (v1.0) ## When you would do this Do this when you first apply for a Stablerail account. We may also ask you to refresh your records later, or if your ownership or business activities change. ## What we ask for and why We verify who owns and controls your company before it can hold or move funds. What we ask for falls into three groups. **Information about your company and how it earns.** Your legal name, registered and operating address, website and business contact details, and the name and position of the person applying. Your industry and a description of your activities, the countries you serve customers in, and any regulatory licences you hold. Your turnover for the last twelve months, whether funds reach you as fiat, stablecoins or both, and how the company generates its income. **Company documents,** usually as certified copies: certificate of incorporation, articles of association or memorandum, register of directors, register of shareholders, an ownership structure chart, and proof of your operating address. **Documents for the people behind the company.** For the ultimate beneficial owner and for one director with account access, we ask for proof of identity and proof of address. For shareholders holding 25 percent or more, proof of identity. For other directors and authorised users, proof of identity and proof of address. Proof of address is normally a utility bill or bank statement from the last three months. ## Steps 1. Open the checklist at https://stablerail.com/checker 2. Answer the questions about your company. The checklist adjusts to your entity type, country and industry, so it tells you what applies to you rather than everything we could ask. 3. Gather the company documents in the form the checklist asks for. Where it says certified copy, a plain scan will not be accepted. 4. Gather identity and address documents for each person the checklist lists. 5. Send everything to your account manager. 6. Answer any follow-up questions we come back with. ## What to expect There is no single fixed list. What we ask for depends on your entity type, your country, your industry, and the level of review applied to your application. That is why the checklist is generated for you rather than published as one document. Review normally takes up to five business days once we have everything. Expect at least one round of follow-up questions, and note that the clock effectively restarts each time we are waiting on you. Complex ownership structures take longer than simple ones. If you plan to use a fiat account, you may be asked to accept our banking partner's terms as a separate step. Your account is opened once verification is complete. ## Common problems and what they mean **"We need a certified copy."** The document must be certified in the way the checklist describes. A photograph or plain scan of the original is not enough. **"Your proof of address has expired."** Utility bills and bank statements must be from the last three months. Ones issued earlier are rejected even if nothing has changed. **"The ownership chart does not reconcile."** The chart and the register of shareholders disagree. Send an updated version of whichever is out of date. **"We need to look through to an individual."** A shareholder holding 25 percent or more is itself a company. We need the ownership of that company too, until we reach the individuals. **"The name does not match."** The name on an identity document differs from the name on the register, often after a change of name. Send the document that connects the two. #### Set up your organisation URL: https://stablerail.com/help/set-up-your-organisation Summary: The five guided steps that turn your verified company into a working account, in the order they appear. Last updated: 2026-08-03 (v1.0) ## When you would do this Do this once, the first time you sign in as the person setting up your company. If a colleague invited you to an existing organisation, you do not do this. See "Sign in and secure your account" instead. You can also run these steps again later if you create a second organisation. ## Steps 1. **Set up your authenticator app.** Scan the code with an authenticator app on your phone, then enter the six-digit code it shows. Save the recovery key you are given somewhere safe and offline. You will need it if you lose your phone. 2. **Register a passkey.** Confirm with your device: Face ID, Touch ID, Windows Hello, or a hardware security key. Use a device you control and expect to keep. 3. **Enter your account and company details.** Your first and last name, your company's legal name, country, business address, phone number, VAT number if you have one, and the currency you want balances displayed in. 4. **Set up your team.** Choose whether you are operating solo or as a team, invite the colleagues who will help run the treasury, and set your signing threshold: how many signers must approve a payment. See "Set your signing quorum". 5. **Choose your policies.** Pick a starting template, Standard or Strict, then adjust the individual controls if you want. See "Set your policy thresholds". Use the **Continue** button to move forward. The step indicators along the top are not clickable, and you cannot skip a step or come back to an earlier one out of order. ## What to expect When you finish the last step, your wallets are created and you land on the dashboard. This takes a moment. You are the Admin of this organisation. That role cannot be granted by invitation, so nobody you invite can become an Admin from the invitation itself. See "Understand roles and permissions". Your policies and signing threshold are not permanent. Both can be changed later, though changing them is itself a governed action that has to be signed. ## Common problems and what they mean **The authenticator code is rejected.** Your phone's clock has drifted from real time. Turn on automatic time setting on the device and try again. **You cannot continue past the team step.** You need enough signers to satisfy the threshold you have chosen. Either invite more signers or lower the threshold. **You lost the recovery key before finishing.** Restart the authenticator step and generate a new one. Do not carry on without saving it. **You do not see your wallets afterwards.** Give the page a moment and refresh. Wallet creation happens at the end of the last step. #### Understand roles and permissions URL: https://stablerail.com/help/understand-roles-and-permissions Summary: The four roles, what each one can do, and the separation-of-duties rules that cannot be switched off. Last updated: 2026-08-03 (v1.0) ## When you would read this Read this before you invite anyone, and whenever you are deciding what access a new joiner should have. ## The four roles Everyone in your organisation has exactly one role. **Admin.** Governance and configuration. The only role that can change the team, the policies, the wallets and the company settings. Holds a signing key and can sign payments. **Signer.** Validates and executes money movement. Can create and sign payments, but cannot change the rules they operate under. Holds a signing key. **Requester.** Prepares work: payment requests, invoices, counterparties. Holds no signing key and can never move money. **Viewer.** Read-only visibility across the workspace, and nothing else. ## What each role can do | Capability | Admin | Signer | Requester | Viewer | |---|:--:|:--:|:--:|:--:| | View everything | Yes | Yes | Yes | Yes | | Create payment requests and batches | Yes | Yes | Yes | No | | Sign and approve payments | Yes | Yes | No | No | | Add and edit counterparties, create invoices | Yes | Yes | Yes | No | | Send bank transfers | Yes | Yes | No | No | | Create and configure wallets | Yes | No | No | No | | Create, edit and publish policies | Yes | No | No | No | | Invite or remove members, change roles | Yes | No | No | No | | Activate banking, manage banking settings | Yes | No | No | No | | Reveal card details | Yes | No | No | No | | Emergency lock | Yes | No | No | No | | View audit log and export evidence | Yes | Yes | Yes | Yes | Anything not listed for a role is blocked. Access is denied by default. ## Rules that cannot be switched off These are enforced by the platform, not by the screen you are looking at. Changing what your browser displays does not change what you are allowed to do. 1. **Admin cannot be invited.** Invitations can only grant Signer, Requester or Viewer. The person who sets the organisation up is the Admin. 2. **Admins are protected.** Only an Admin can remove an Admin, the last Admin can never be removed or demoted, and nobody can change their own role. 3. **Signers cannot rewrite the rules.** A Signer can approve a payment but cannot edit the policy that governs it. 4. **No self-approval above your limit.** If the person who requested a payment is also a signer, anything above your self-approval limit needs a second, independent signature. 5. **Requesters and Viewers hold no key.** No configuration can give them the ability to sign. ## Common problems and what they mean **"The Sign button is missing."** You are a Requester or a Viewer, or the payment is blocked. Only Admins and Signers can sign. **"I cannot edit policies."** Only Admins can. Ask an Admin. **"I cannot change my own role."** Nobody can. Ask another Admin. #### Set your signing quorum URL: https://stablerail.com/help/set-your-signing-quorum Summary: How many signers must approve a payment, where you set it, and what changes when you add or remove a signer. Last updated: 2026-08-03 (v1.0) ## When you would do this Set your quorum during setup, at the team step. Revisit it whenever the size of your team changes, or when you want tighter or looser control over money movement. ## What a quorum is Your quorum is the number of signers who must approve a payment before it executes, written as "2 of 3": two approvals needed, three people able to give them. Only Admins and Signers count towards a quorum. Requesters and Viewers hold no signing key, so adding them does not change your numbers. A quorum of 1 means any single signer can send on their own, subject to your policy limits. Higher numbers are safer and slower. ## Steps 1. Go to **Settings › Team**. 2. Check how many people currently hold a signing key. That is the upper bound on your threshold. 3. Invite any additional signers you need, and wait for them to accept and complete their security setup. A signer who has not finished setup does not yet count. 4. When you invite a signer, the invitation screen asks whether to keep your current threshold or increase it. Choose deliberately. 5. To change the threshold on its own, an Admin makes the change and it is queued as a governance item. 6. Open **Operation › Signing** and sign the queued quorum change. ## What to expect A quorum change is not a setting that saves instantly. It is a governed action: it goes to the signing queue as a "Signer quorum change" and takes effect only once the required signatures are collected. Your threshold can never exceed the number of people holding a key. If you remove a signer and that would leave you unable to meet your own threshold, resolve the threshold first. Payments already in the signing queue when the change takes effect keep the rules they were created under. ## Common problems and what they mean **"You need more signers."** The threshold you picked is higher than the number of people holding a key. Invite another signer or lower the threshold. **"1 of 2 signed" and nothing is happening.** The payment is waiting for a second person. Quorum is working as designed. Ask the other signer to open the signing queue. **A signer you invited does not count yet.** They have accepted the invitation but not finished setting up their authenticator app and passkey. They hold no key until they do. **You are the only signer.** Extra safeguards apply, including dual verification when you pay a first-time address. See "Set your policy thresholds". #### Invite and remove team members URL: https://stablerail.com/help/invite-and-remove-team-members Summary: Adding colleagues, choosing their role, managing pending invitations, and removing people who leave. Last updated: 2026-08-03 (v1.0) ## When you would do this When someone joins your finance or operations team, when someone changes responsibilities, or when someone leaves. Only an Admin can do any of this. ## Steps: invite someone 1. Go to **Settings › Team**. 2. Select **Invite Member**. 3. Enter their full name and work email address. 4. Choose their role: Signer, Requester or Viewer. Admin is not offered, by design. 5. If you are adding a signer, decide whether to keep your current signing threshold or increase it. The screen shows you both options with the resulting numbers. 6. Select **Send Invitation**. They receive an email with a link. They must open it and sign in **with the same email address the invitation was sent to**, then complete their own authenticator and passkey setup. ## Steps: remove someone 1. Go to **Settings › Team**. 2. Find the person and remove them. 3. If they held a signing key, check your signing threshold still makes sense with one fewer signer. ## Managing pending invitations Invitations that have not been accepted appear under **Pending Invites**, with their expiry date. For each one you can resend it, copy the link to send yourself, or revoke it. An invitation that has expired can be resent with a new link. Declined and expired invitations stay visible so you can see what happened. ## What to expect Invited people do not appear as team members until they accept and finish setting up their security. A signer who has accepted but not finished setup does not yet count towards your quorum. Role changes are made from the team list, not by re-inviting. ## Common problems and what they mean **"This email already has a pending invite."** Revoke the existing invitation first, then send a new one with the role you want. **"This person declined an earlier invite."** Revoke the declined invitation before inviting them again. **"This person is already a team member."** Change their role from the team list instead of inviting them again. **"Invite created but email delivery failed."** The invitation exists but the email did not arrive. Use the resend button, or copy the link and send it yourself. **They signed in and got no access.** They used a different email address from the one the invitation was sent to. Revoke and re-invite to the address they actually use. **You cannot remove an Admin.** Only another Admin can, and the last Admin can never be removed. #### Sign in and secure your account URL: https://stablerail.com/help/sign-in-and-secure-your-account Summary: How signing in works, what to do on a new device, and how sessions expire. Last updated: 2026-08-03 (v1.0) ## When you would do this Every time you use Stablerail, and whenever you set up a new device. ## Steps 1. Go to the sign-in page and enter your work email address. 2. Enter the one-time code emailed to you. 3. Confirm with your passkey: Face ID, Touch ID, Windows Hello, or your hardware security key. 4. Enter the six-digit code from your authenticator app. If a passkey is not available on the device you are using, you may be able to sign in with the email code and authenticator code alone. This is recorded in the audit log as a fallback sign-in. ## Setting up a new device Your authenticator app moves with you if your authenticator supports it, or can be set up again using your recovery key. A passkey is tied to a device. Register a passkey on each device you use regularly rather than relying on the fallback every time. ## Sessions You are signed out automatically after **15 minutes** without activity, and again after a longer fixed period even if you have been active the whole time. Sign back in to continue. Anything already in the signing queue is unaffected. If you belong to more than one organisation, you act inside one at a time and switch between them from the organisation switcher. Only an Admin can create a new organisation. ## Protecting your account - Register your passkey and authenticator on a device you control and expect to keep. - Store your recovery key offline, not in the same password manager you sign in with. - Do not share sign-in codes with anyone, including anyone claiming to be from Stablerail. We will never ask for one. - Review **Governance › Audit log** occasionally. Fallback sign-ins and unusual activity are recorded there. - Keep **Settings › Account** email preferences switched on for the notifications you want. Critical login and security emails are always sent and cannot be turned off. ## Common problems and what they mean **The authenticator code is rejected.** Your device clock has drifted. Turn on automatic time setting and try again. **Your passkey is not recognised on this device.** You have not registered one here. Use the email and authenticator fallback, then register a passkey on this device. **You are stuck in a sign-in loop.** Confirm you are using the email address your account was created with. If it persists, contact support. **You joined but see no organisation.** You signed in with a different email address from the one your invitation was sent to. Ask your Admin to revoke and re-invite to the correct address. **You lost your device.** See "Recover access to your account". ### Wallets and balances How self-custody works here, creating wallets, and reading your balances. #### How self-custody works here URL: https://stablerail.com/help/how-self-custody-works Summary: What it means that Stablerail cannot move your funds, and what that puts in your hands. Last updated: 2026-08-03 (v1.0) ## When you would read this Read this before you fund your first wallet, and when you need to explain to your board or your auditor who can actually move the company's money. ## What self-custody means here Your funds sit in wallets that belong to your organisation. Stablerail operates the platform around them. We cannot move your money. A payment can only leave a wallet if the required number of your authorised people approve it. Stablerail cannot supply that approval, cannot substitute for it, and cannot override it. There is no administrative route by which we release your funds, with or without your knowledge. Your control is expressed through **approval and signing**. It is not a file or a phrase you keep on your laptop. When you approve a payment, you are exercising the control. When you refuse, nothing happens. Only Admins and Signers hold signing capability. Requesters and Viewers never do, under any configuration. ## What this puts in your hands **You decide who can approve.** Your roles and your signing quorum determine who can move money and how many of them are needed. See "Set your signing quorum". **You decide the rules.** Your policies determine what needs a second signature, what needs supporting documents, and what gets flagged. See "What the policy engine controls". **You carry the consequences of losing access.** We cannot recover signing keys for you. If your people lose their devices, recovery runs through a support procedure, not through us unlocking your funds. See "Recover access to your account". **You carry your own compliance obligations.** We screen every payment and record everything. What you do with those results, and what your regulator expects of you, is yours. ## What to expect Day to day this is invisible. You create a payment, it gets screened, someone approves it, it goes. It becomes visible in three places: when a payment needs a second approver and that person is unavailable, when a payment is blocked and nobody can override it, and when someone loses a device. Each of those is the design working, not a fault. ## Common questions **Can Stablerail move our funds if compelled?** No. We cannot produce the approvals a payment requires. **Can Stablerail freeze our account?** Your Admin can engage an emergency lock that halts payments. Platform-level restrictions are governed by your agreement with us. **What if Stablerail is unavailable?** Your funds remain yours. They are not held by us. **Can we get our keys out?** Wallet key export is available. Speak to your account manager about the process, which is deliberately restricted. #### Supported networks and assets URL: https://stablerail.com/help/supported-networks-and-assets Summary: Which blockchains and tokens you can hold and move, and why the network always matters. Last updated: 2026-08-03 (v1.0) ## When you would read this Before you create a wallet, before you give a counterparty an address to pay you on, and any time someone sends you an address and you are not sure it will work. ## Supported networks - Ethereum - Arbitrum - Base - Optimism - Polygon - BNB Chain - Solana - Tron - Bitcoin - Litecoin - Bitcoin Cash - XRP ## Supported assets Stablecoins: USDC, USDT, EURC, DAI, PYUSD. Native coins: ETH, BTC, LTC, BCH, XRP, SOL, TRX, BNB, POL. Not every asset exists on every network. When you create a wallet or build a payment, the app only offers the combinations that are actually available, so use the selectors rather than working from this list. ## Why the network matters A wallet address belongs to a specific network. The same address format can be valid on several networks, and an address that looks correct can still be the wrong one for the network you are sending on. **Stablerail does not currently check that a recipient address belongs to the network you selected.** If you send on the wrong network, the payment is signed and broadcast like any other, and the funds cannot be recovered by Stablerail or by anyone else. This is the single most expensive mistake available to you in the product. Treat the network field with the same care as the amount. ## How to avoid getting it wrong 1. Ask your counterparty for the network in writing, not just the address. 2. Save the address against a counterparty with the correct network recorded, and pay from the counterparty record rather than pasting an address each time. See "Add a counterparty". 3. On a first payment to a new address, send a small amount, confirm it arrived, then send the rest. 4. Check the network shown on the review screen before you approve, not just the address. ## Common problems and what they mean **"Unknown chain for address."** The address does not match any network Stablerail supports, or the chain you selected does not fit the address format. Recheck both with your counterparty. **Your counterparty says the funds never arrived, but the ledger shows the payment settled.** The payment succeeded on the network you chose. If that was not the network they expected, the funds are at that address on the network you sent on. Contact your account manager. **An asset you expected is not in the list.** It is not available on the network you selected. Try another network, or ask your account manager whether it is supported at all. #### Create a wallet URL: https://stablerail.com/help/create-a-wallet Summary: Adding a vault to hold your funds, and attaching a policy so it is governed. Last updated: 2026-08-03 (v1.0) ## When you would do this When you want to separate funds by purpose: operations, payroll, reserves, one per entity, one per network. Only an Admin can create a wallet. Wallets are called **vaults** in the app. A vault requires your signing quorum to move funds out of it. ## Steps 1. Go to **Governance › Vaults**. 2. Select **Add Vault**. 3. Give it a name that will still make sense to someone else in a year. "Operations EUR" is better than "Vault 2". 4. Choose the blockchain it will operate on. 5. Choose the key quorum that will govern it. 6. Select **Create Vault**. ## Attaching a policy A vault is governed by a policy. From the vault's actions you can **Assign Policy** or **Remove Policy**. Both are governed actions. They do not take effect when you click them. They are queued to the signing queue and require signatures before they apply. Assigning a policy enables transaction governance and self-approval controls on that vault. Removing one detaches the vault from your policy and disables those controls, so only do it deliberately. ## What to expect The vault appears on the Vaults page with its balance and its positions by chain. You can drag vaults to reorder them. The page header shows your totals across all vaults: total value, number of vaults, number of positions, and number of quarantine addresses. Balances update after transactions settle on the network. There is a short delay after a payment or deposit. **Refresh balances** forces a fresh check. Each vault shows a wallet risk score, which reflects screening of the addresses it has interacted with. ## Common problems and what they mean **"Add Vault" is not available.** You are not an Admin. Only Admins create vaults. **"Please select a key quorum" or "Please select a blockchain."** Both are required. Neither has a default, on purpose. **The vault shows no positions.** Nothing has been received into it yet. Its address is on the Receive page under Direct Deposit. **Your policy change has not applied.** It is waiting in the signing queue. Open **Operation › Signing** and sign it. **You created a vault on the wrong network.** Create another one on the correct network. Do not send funds to the first one on the assumption it will work. #### Use a quarantine address URL: https://stablerail.com/help/use-a-quarantine-address Summary: One-time receiving addresses that keep unknown or high-risk deposits away from your treasury. Last updated: 2026-08-03 (v1.0) ## When you would do this Use a quarantine address when you are receiving from someone you do not know well, from a counterparty you have not screened, or in any situation where you would rather inspect the funds before they touch your main balances. A quarantine address is a separate receiving address you hand out instead of your treasury address. Funds arrive there, you review them, and only then do you move them in. If the sender turns out to be a problem, the problem is contained in an address you can archive rather than sitting in your operating vault. It also protects against address poisoning, where an attacker seeds your transaction history with an address that looks like one of yours in the hope that someone later copies the wrong one. ## Steps: create one 1. Go to **Operation › Receive**, or to **Governance › Vaults**. 2. Select **New Quarantine Address**. 3. Give it a label that identifies who it is for. 4. Share that address with the sender instead of your treasury address. ## Steps: review and move the funds in 1. When funds arrive, open the quarantine address and check what landed: asset, amount, network, and the risk result on the deposit. 2. If you are satisfied, use **Internal Transfer** to move the funds to your main vault. 3. If you are not, leave them where they are and speak to your account manager before moving anything. ## Steps: archive it 1. Open the quarantine address and select **Archive**. 2. If it still holds assets, the dialog tells you so and lists what needs moving. Transfer the funds to your main vault first. 3. Once there are no balances left, confirm **Archive Address**. Archiving hides the address from your activity views. It does not delete anything. The address and everything that happened at it remain in the audit trail. ## What to expect Quarantine addresses are counted separately on the Vaults page so you can see how many are open. They are ordinary addresses in every other respect. Deposits into them are screened like any other deposit, and appear in your ledger. ## Common problems and what they mean **"This address holds assets."** You cannot archive an address with a balance. Move the funds out first. **"No balances found."** Nothing arrived, or it arrived on a different network from the one you are looking at. **You gave out a quarantine address and then archived it.** Funds sent to it afterwards still arrive. Archiving hides the address from your views, it does not close it. Tell the sender to stop using it, and archive an address only once you are sure nothing further is coming. #### View balances and history URL: https://stablerail.com/help/view-balances-and-history Summary: Where to find what you hold, what has moved, and the on-chain record behind each transaction. Last updated: 2026-08-03 (v1.0) ## When you would do this Daily, to see where your money is. At month end, to reconcile. Whenever someone asks what happened to a specific payment. ## Where to look **Governance › Vaults** shows what you hold. Each vault lists its balance and its positions broken down by chain, and the header totals everything across your vaults. **Operation › Ledger** shows what has moved. Every completed transaction, incoming and outgoing, with its amount, counterparty, network and status. **Dashboard** gives you the short version of both. ## Steps: find a specific transaction 1. Go to **Operation › Ledger**. 2. Filter by date, direction, vault, asset or status, or search. 3. Open the transaction to see the full detail: timeline, risk result, counterparty, network, and the on-chain transaction reference. 4. From the detail view you can download the receipt, the evidence pack, or the invoice if one is attached. ## Steps: export your history 1. On the Ledger, choose **Export**. 2. Pick PDF, Excel or CSV. ## Refreshing balances Balances update once transactions settle on the network. After a payment or a deposit there is a short delay while the network confirms. **Refresh balances** on the Vaults page forces a fresh check rather than waiting. ## Common problems and what they mean **A deposit has not appeared.** Give the network time to confirm, then refresh balances. If it still does not appear and you can see it on a block explorer, use **Import transaction** on the Ledger: paste the explorer link and Stablerail will fetch it. The dialog tells you whether it will import it, update an existing record, or that the destination is not one of your wallets. **"Not your wallet."** The transaction you pasted did not go to an address belonging to your organisation. Check the address on the explorer against your vault addresses. **Your balance looks wrong after a payment.** The network fee is deducted from the sending wallet in addition to the amount sent. On some networks that fee comes out of a native coin balance rather than the asset you sent. **Lots of tiny unrecognised balances.** These are usually unsolicited dust deposits, sometimes used in address-poisoning attempts. Filter them out with the dust filter, and never copy an address out of your transaction history. **Numbers disagree with your accounting system.** Export the ledger and reconcile against the on-chain references, which are the authoritative record of what moved. ### Making payments Creating, approving and signing payments, batch payouts, and what happens when one fails. #### Create a payment request URL: https://stablerail.com/help/create-a-payment-request Summary: Preparing an outbound payment and sending it for approval, whether to a saved counterparty or a new address. Last updated: 2026-08-03 (v1.0) ## When you would do this Whenever you need to pay someone. Admins, Signers and Requesters can all create a payment. Creating one does not send it. ## Steps 1. Go to **Operation › Pay**. 2. Choose the tab that fits: **Counterparty** to pay someone in your directory, **New Address** to pay an address you have not saved, **Internal** to move funds between your own vaults, or **Batch** to pay many recipients at once. 3. Choose the **source vault** to pay from. 4. Choose the recipient. On the Counterparty tab, pick the counterparty and then which of their registered addresses to use. The screen shows when you last paid them and how much. 5. Enter the **amount** and confirm the **asset and network**. Check the network carefully. See "Supported networks and assets". 6. Attach documentation if your policy requires it, or if it will help whoever approves this. 7. Select **Run checks**. 8. Review the risk result, then confirm to send it to the signing queue. ## Paying a new address The **New Address** tab asks for a written **reason** justifying payment to an unverified address. This is not a formality: it is what an approver and later an auditor will read. You can save the address as a counterparty at the same time, which is worth doing for anyone you expect to pay again. ## What to expect Once you confirm, the payment becomes a request waiting in **Operation › Signing**. It has not moved any money. What happens next depends on the risk result: - **PASS**: it is ready to sign. - **FLAG**: it is created but locked. Someone must resolve the flag before it can be signed. See "Resolve a flagged payment". - **BLOCK**: it cannot be sent. It can only be rejected and archived. If you are a Requester, your work is done. A Signer or Admin takes it from here. If you are a Signer and the amount is within your self-approval limit, you may be able to sign it yourself immediately. Above that limit it needs a second person. See "Understand self-approval limits". ## Common problems and what they mean **"This counterparty has no registered addresses."** Add one on the counterparty record first. **Checks sit on "Checking" for a while.** Screening is running. You can cancel the request while it is checking if you created it in error. **"Unusually high network fee."** The network is congested. You can wait, or choose a slower fee option, or proceed. **The amount field will not accept your figure.** You are trying to send more than the vault holds, or more than is spendable once the network fee is reserved. #### Approve and sign a payment URL: https://stablerail.com/help/approve-and-sign-a-payment Summary: Working the signing queue: what each status means, what to check before you approve, and how quorum progresses. Last updated: 2026-08-03 (v1.0) ## When you would do this When something is waiting for your approval. The Signing item in the sidebar carries a badge with the number of items awaiting action. Only Admins and Signers can sign. ## Steps 1. Go to **Operation › Signing**. 2. Filter if the queue is long: All, Passed, Flagged, Blocked, Checking. 3. Open the item and read the request: who requested it, when, the amount, the source vault, the destination, the network, and the stated reason. 4. Read the **policy checks** and the risk result. Do not skip this. It is the part that protects you. 5. Check the signature progress, shown as collected out of required. 6. Sign. ## What to check before you approve - Is the **destination address** the one you expect? Compare it against the counterparty record, not against an email. - Is the **network** right? - Does the **amount** match the invoice or instruction you are approving against? - Does the **reason** make sense, and does the supporting document actually support it? - Is anything about the timing or the recipient unusual? You are the control. If something looks wrong, do not sign it. Rejecting a correct payment costs an hour. Approving a wrong one costs the money. ## What the statuses mean - **PASS**: checks found nothing unusual. Ready to sign. - **FLAG**: something needs attention. Resolve the flag before signing. See "Resolve a flagged payment". - **BLOCK**: not permitted. It cannot be signed at all, only rejected and archived. - **CHECKING**: screening is still running. - **Governance**: not a payment but a change to your setup, such as a policy update, a policy removal or a signer quorum change. These are signed the same way. ## What to expect If only one approval is required and the item has passed, signing sends it immediately. If more than one approval is required, your signature is added and the item stays in the queue showing progress such as "1 of 2 signed". It executes once the last required signature arrives. You can see who has signed. Where more than one approval is required, the person who created the payment cannot be the only approver. Once the final signature is given and the payment is broadcast, it cannot be recalled. See "What can and cannot be reversed". ## Common problems and what they mean **The Sign button is missing.** You are a Requester or Viewer, or the item is blocked, or you have already signed it. **"Violation detected."** The payment breaks a policy and cannot be signed. Cancel the request and create a compliant one. **"Expired."** The item sat too long and its signing window closed. Create it again. **It says "Self-approved" but nothing sent.** The amount was within a self-approval limit, but another check is still holding it. Read the policy checks. **Nothing happens after you sign.** You were not the last required signer. Check the signature count. #### Understand self-approval limits URL: https://stablerail.com/help/understand-self-approval-limits Summary: When one signer can send alone, when a second is required, and how the different limits interact. Last updated: 2026-08-03 (v1.0) ## When you would read this When you want to know why one payment went straight through and another is waiting for a colleague. Also before you change the limits, because they are the main dial between speed and safety. ## What a self-approval limit is A self-approval limit is the amount below which a single signer can create a payment and send it without anyone else approving. Above that amount, your full signing quorum applies and a second, independent signer must approve. It exists so that routine payments move quickly while larger ones get a second pair of eyes. ## The separate limits Stablerail keeps several self-approval limits, because the risks are not the same. **External payments.** Payments out to third parties. This is the limit most people mean. It can also be switched off entirely, in which case every external payment needs at least one additional signer. **Swaps.** Exchanging one asset for another. Funds stay under your control throughout, so this limit is configured separately. It can also be switched off, making every swap require quorum. **Earn.** Deposits into and withdrawals from yield vaults. Can be set to allow a single signer, or to require full quorum. **Internal transfers.** Moving funds between your own vaults, with its own limit and its own auto-approval setting. **Native coins.** Limits on stablecoin payments are set in your display currency. Native coins such as ETH, BTC or SOL have their own separate per-coin limits, entered in units of that coin. Until you enable and configure them, native coin payments require full quorum. ## What to expect The limit is evaluated when the payment request is created, against the policy in force at that moment. Changing a limit does not retrospectively change payments already in the queue. Being under the limit is not a guarantee of a quick send. Other controls still apply: a flag from screening, a new recipient, or a missing document will hold a payment regardless of its size. If you are the only signer in your organisation, additional safeguards apply, including dual verification when paying a first-time address. ## Common problems and what they mean **A small payment still needs a second signer.** Something other than the amount is holding it: a new recipient, a required document, or a flag. Read the policy checks on the item. **A swap went through alone but a smaller payment did not.** They use different limits. Swaps have their own. **A native coin payment always needs quorum.** Native token limits have not been enabled and configured. Until they are, full quorum is required for those coins. **Nobody can raise the limit.** Only an Admin can, and the change has to be signed. See "Edit policies safely". #### Send a batch payout URL: https://stablerail.com/help/send-a-batch-payout Summary: Paying many recipients in one approved run, from building the payee batch to signing it. Last updated: 2026-08-03 (v1.0) ## When you would do this Payroll, contractor runs, supplier settlement, any time you are paying a list of people rather than one. A batch is approved and signed once, as a single item, rather than one approval per recipient. ## Steps: build the payee batch 1. Go to **Governance › Counterparty** and open **Batches**. 2. Create a new batch and give it a name. 3. Pick the **chain**. Every address in the batch must belong to it. 4. Add members, either by selecting counterparties individually or by bulk import. 5. To bulk import, download the template first. The Excel template is recommended because the address column is a dropdown of your counterparties on the selected chain, which prevents most mistakes. CSV works as a plain-text fallback. 6. Upload your file. Before anything is imported you get a preview showing how many rows are valid, how many have errors, and how many have warnings. Fix the errors and re-upload. 7. Import the members, then save the batch. There is a maximum number of members per batch, shown on the import dialog. ## Steps: pay the batch 1. Go to **Operation › Pay** and choose the **Batch** tab. 2. Select the payee batch. This loads the recipients and locks the asset. 3. Choose the **source vault**. It must hold the asset on the batch's network. 4. Review the payment lines. You can edit amounts and remove recipients here without changing the saved batch. 5. Check the total. 6. Select **Run Checks**. 7. Review the batch risk result, then send it to the signing queue. 8. Sign it in **Operation › Signing**. ## What to expect A batch takes the risk level of its riskiest member. If any single recipient is blocked, the entire batch is blocked. If any recipient is flagged, the batch is flagged. If **Strict Payout Mode** is on and the batch contains any address that is new to you, the whole batch is flagged for Admin review. When the batch executes, each recipient is paid. The Ledger shows the batch with its recipients and their individual statuses. ## Common problems and what they mean **"No source vault is available for this network family."** You do not have a vault on the batch's chain. Create one, or rebuild the batch on a chain you already hold funds on. **"Selected payee batch is missing chain or asset setup."** The batch was saved without a chain or asset. Open it in Counterparties and complete it. **"No balance found."** The source vault does not hold the asset. Fund it or pick another vault. **Rows rejected on import.** The address does not belong to the selected chain, is not a registered counterparty address, or the amount is not a valid number. The preview names the row. **One recipient blocks everything.** That is deliberate. Remove that recipient from the payment lines and pay them separately once resolved. #### Network fees and gas sponsorship URL: https://stablerail.com/help/network-fees-and-gas-sponsorship Summary: Why a payment costs more than the amount you sent, how to choose a speed, and what gas sponsorship covers. Last updated: 2026-08-03 (v1.0) ## When you would read this When your balance moved by more than the amount you sent, when a payment is taking longer than expected, or when you are planning a large run of payments. ## What a network fee is Every blockchain charges a fee to process a transaction. It is paid to the network, not to Stablerail, and it is unavoidable. It varies with how busy the network is at that moment, so the same payment costs different amounts at different times. On most networks the fee is paid in that network's native coin, not in the asset you are sending. Sending a stablecoin can therefore require a small balance of the network's native coin as well. Stablerail estimates the fee before you confirm and shows it on the payment screen. ## Choosing a speed On networks where it applies you can choose how much to pay for how fast: - **Fast**, roughly ten minutes - **Normal**, roughly an hour - **Slow**, two hours or more These are estimates from current network conditions, not guarantees. If the network gets busier after you send, a slow transaction can take considerably longer. Choose Fast when someone is waiting. Choose Slow for routine runs where an hour or two does not matter. ## Gas sponsorship Gas sponsorship means Stablerail covers the network fee for a transaction so your wallet does not need to hold the network's native coin to transact. It is available on Tron, on the EVM networks, and on Solana. You do not switch it on per payment. Where it applies, it applies. Any charges associated with it are set out in your Order Form. Your account manager can confirm what applies to your account. ## Common problems and what they mean **"Unusually high network fee."** The estimate is well above normal for that network, usually short-lived congestion. Wait and retry, choose a slower speed, or accept it if the payment is urgent. **"Network fee estimate unavailable."** Stablerail could not reach the network for a current estimate. Retry shortly rather than sending blind. **Your balance dropped by more than you sent.** The fee came out on top of the amount. **A payment will not send and you hold plenty of the asset.** You may be short of the network's native coin needed to pay the fee, on a network where sponsorship does not apply. **A slow payment has not confirmed.** Give it time. If it is far past the estimate, see "Fix a payment that fails or stalls". #### Fix a payment that fails or stalls URL: https://stablerail.com/help/fix-a-payment-that-fails-or-stalls Summary: How to tell where a payment is stuck, what you can resolve yourself, and when to contact support. Last updated: 2026-08-03 (v1.0) ## When you would do this When a payment has not arrived and your counterparty is asking, or when something has been sitting in the signing queue longer than you expected. ## Steps: find out where it actually is 1. Open **Operation › Signing** and look for it there first. 2. If it is not in the signing queue, open **Operation › Ledger** and find it there. 3. Open the item and read the **timeline**. It tells you which stage it reached and when. Where it is determines what you can do. ## Still in the signing queue The payment has not been sent. Nothing has left your account. - **Checking**: screening is still running. Wait. - **Flagged**: it needs a flag resolved before anyone can sign. See "Resolve a flagged payment". - **Blocked**: it will not be sent. Reject and archive it. - **Waiting on signatures**: it shows progress such as "1 of 2 signed". Chase the other signer. - **Expired**: the signing window closed. Create the payment again. While a payment is in the queue you can cancel it. Cancelling stops the compliance check and marks the request cancelled. It cannot be undone, but no money has moved. ## Broadcast but not confirmed The payment has been sent to the network and is waiting to be included. The Ledger shows it as pending with an on-chain reference. You cannot cancel or speed this up from Stablerail. A payment sent at a slow fee during congestion can take much longer than the estimate. Wait, and check the on-chain reference on a block explorer if you want to see the network's own view. ## Settled but the recipient says it did not arrive The payment reached the address on the network you chose. Check both against what the recipient expected. If the network was wrong, see "What can and cannot be reversed", and contact your account manager. ## When to contact support Contact support when a payment has been broadcast and appears genuinely stuck rather than slow, when the timeline stops at a stage you cannot explain, or when the Ledger and the network disagree. There is no self-service retry for a broadcast payment, so this needs us. Have the transaction reference ready. ## Common problems and what they mean **Nothing happens after you sign.** You were not the last required signer. **"Violation detected."** A policy blocks it. Cancel and create a compliant payment. **An incoming deposit never appeared.** Use **Import transaction** on the Ledger with the explorer link. See "View balances and history". **Everything is stuck at once.** Check whether an emergency lock is engaged, on **Settings › Security**. #### What can and cannot be reversed URL: https://stablerail.com/help/what-can-and-cannot-be-reversed Summary: The point of no return for a payment, and what your options are on either side of it. Last updated: 2026-08-03 (v1.0) ## When you would read this Before you approve anything large, and immediately if you think a payment has gone wrong. ## The point of no return A payment can be stopped at any time **until the last required signature is given**. After that it is broadcast to the network, and it cannot be recalled by you, by your counterparty, or by Stablerail. There is no pending window in which we can pull it back. There is no reversal, no chargeback and no dispute process on a blockchain payment. ## What you can reverse **A request that has not been fully signed.** Cancel it from the signing queue. No money has moved. **A request that is still being screened.** Cancel it. The compliance check stops and the request is marked cancelled. **A blocked payment.** It cannot be sent at all. Reject and archive it. **A draft or unsent invoice.** Edit or cancel it. **An unaccepted invitation.** Revoke it. **A queued governance change**, such as a policy update or quorum change. If it has not collected its signatures, it has not taken effect. ## What you cannot reverse **A broadcast payment.** Once signed and sent, the funds are gone from your wallet. **A payment to the wrong address.** If the address was valid, the funds are at that address. Whoever controls it decides whether to return them. Your only route is asking them. **A payment on the wrong network.** Stablerail does not currently check that a recipient address belongs to the network you selected. If you choose the wrong one, the payment is signed and broadcast normally and the funds cannot be recovered by Stablerail or anyone else. Contact your account manager, but treat this as unrecoverable. **A closed card.** Closing is permanent. Freeze instead if you might want it back. **An executed fiat transfer.** Bank transfers may sometimes be returned by the receiving bank, but that is the bank's decision and not something Stablerail controls. See "Send funds from your fiat account". ## How to protect yourself 1. Pay from saved counterparty records rather than pasting addresses. 2. Never copy an address out of your transaction history. That is exactly what address-poisoning attacks rely on. 3. On a first payment to a new address, send a small amount and confirm receipt before sending the rest. 4. Check the network on the review screen every time. 5. Keep a quorum above one for meaningful amounts. A second reader catches what the first one misses. ### Counterparties Your directory of the people and companies you pay and receive from. #### Add a counterparty URL: https://stablerail.com/help/add-a-counterparty Summary: Saving the people and companies you pay, so you never have to paste an address again. Last updated: 2026-08-03 (v1.0) ## When you would do this Before you pay anyone for the first time, and certainly before you pay them a second time. Admins, Signers and Requesters can all add counterparties. Paying from a saved counterparty rather than a pasted address is the single most effective habit for avoiding a misdirected payment. ## Steps 1. Go to **Governance › Counterparty**. 2. Select **Add Counterparty**. 3. Choose the **type**: Vendor, Customer, Investor, Employee, Contractor, Subsidiary, Institution, Exchange or Crypto Service Provider. This drives how they are grouped and reported. 4. Choose the **entity type**: Business or Individual. A business asks for a company name and a contact person. An individual asks for a first and last name. 5. Add contact details: email, phone, and VAT number if they have one. 6. Add one or more **wallet addresses**. For each, pick the chain, paste the address, and give it a label such as Primary or Payroll. 7. Add internal notes if useful: payment terms, contract references, special instructions. These are for your team, not for the counterparty. 8. Save. ## Adding many at once To load an existing supplier list, use **Bulk Import Counterparties**. Download the template first. The Excel version is recommended because the chain field is a dropdown, which prevents the most common import error. Upload your file and review the preview, which shows how many rows are valid and which have errors, before anything is created. ## What to expect Wallet addresses are screened for risk when you submit. A counterparty whose address screens badly will show a risk tier on their record. A newly added address starts as **new**. It becomes **known** after a completed transaction to it. Paying a new address above your new-recipient threshold raises a flag for review, which is intentional friction on first payment. The counterparty then appears in the Pay screen's counterparty picker, along with when you last paid them and how much. ## Common problems and what they mean **"Please enter a valid wallet address."** The address does not match the format for the chain you selected. Confirm both with the counterparty. **Name rejected.** The name fields restrict which characters are allowed. Remove unusual punctuation. **The address screened as high risk.** Do not proceed on your own judgement. See "Read a counterparty's risk profile and history". **They need paying on several networks.** Add one address per network on the same counterparty record rather than creating duplicates. #### Manage counterparty addresses safely URL: https://stablerail.com/help/manage-counterparty-addresses-safely Summary: Why an address cannot be edited, what to do when a counterparty changes their details, and how to archive safely. Last updated: 2026-08-03 (v1.0) ## When you would do this When a supplier emails to say their payment details have changed. This is the most common fraud scenario in business payments, and how you handle it matters more than almost anything else in this help centre. ## The rule: addresses are added, never edited You cannot edit a saved wallet address. You can change its **label**, and nothing else. If a counterparty changes their address, you add the new one and archive the old one. There is no path that quietly rewrites an existing address in place. This is deliberate. If addresses were editable, one compromised email account plus one careless edit would redirect every future payment to that counterparty, with nothing in the record showing what changed. ## Steps: a counterparty changes their address 1. **Do not act on the email.** Treat any request to change payment details as suspect by default, however routine it looks. 2. **Verify out of band.** Phone a number you already have on file, not one from the email. Speak to a person you know. Confirm the full address with them. 3. Open the counterparty in **Governance › Counterparty**. 4. Select **Add Address**, choose the chain, paste the new address, and label it clearly with the date. 5. **Archive the old address** so nobody pays it by habit. 6. Send a small test payment, confirm receipt with the counterparty, then resume normal payments. ## Archiving Archiving an address removes it from the pickers so it cannot be selected for a new payment. It does not delete anything: the address and every payment made to it remain in the audit trail. You can restore an archived address if you archived it in error. Archived addresses are shown as a count on the counterparty record. You can also archive an entire counterparty, and restore it later. ## What to expect If a counterparty record shows **Address Change Locked**, one or more of its addresses have pending changes that stay locked until verification is complete. You cannot pay a locked address until that clears. A newly added address is **new** until a payment to it completes, at which point it becomes **known**. A new address above your new-recipient threshold raises a flag on first payment. ## Common problems and what they mean **You cannot find an edit button for the address.** There is not one. Add and archive instead. **The old address is still being used in a batch.** Payee batches hold their own member list. Update the batch as well as the counterparty. **You archived the wrong address.** Restore it from the counterparty record. **A payment to a newly added address is flagged.** Expected. Resolve the flag with the verification you did. See "Resolve a flagged payment". #### Read a counterparty's risk profile and history URL: https://stablerail.com/help/read-counterparty-risk-and-history Summary: What the risk tier on a counterparty means, and how to use their payment history before you approve. Last updated: 2026-08-03 (v1.0) ## When you would do this Before approving a first payment to someone, when a payment to them is flagged, and periodically for counterparties you pay regularly. ## Steps 1. Go to **Governance › Counterparty** and open the counterparty. 2. Read the **risk tier** on the header. This reflects screening of their registered addresses. 3. Open **Registered Addresses**. Each row shows the chain, the address, its status, its risk score, and when it was added. 4. Check the status of the address you are about to pay: **new**, or **known** after a completed payment to it. 5. Review their payment history: what you have paid them, when, and on which network. The Pay screen also surfaces this. When you select a counterparty it shows when you last paid them and how much, so you can sanity-check a new request against the pattern. ## How to read it **Risk tier** is about the addresses, not about your commercial relationship. A long-standing supplier can acquire a worse tier because an address they use has interacted with something screening dislikes. **A new address** is not a red flag on its own. It means no completed payment has gone to it yet. Every legitimate address starts here. **A high risk score with a plausible story** still needs a decision from a person. Screening tells you what it found. It does not tell you whether to pay. **No history at all** for a counterparty you believe is long-standing usually means someone created a duplicate record. Check for duplicates before paying. ## What to expect Risk information updates as screening runs, so a counterparty's tier can change without you doing anything. See "Ongoing wallet risk monitoring". Anything you decide should go into the record. If you approve a payment to a counterparty whose tier is poor, resolve the flag with a comment and a document explaining why. That comment is what your auditor reads later, and what protects the person who approved it. ## Common problems and what they mean **The tier got worse and nothing changed on your side.** Re-screening found something new about an address they use. Look at which address, and consider asking them to receive on a different one. **A counterparty has two records.** Someone added them twice, often once as a business and once as an individual. Archive the duplicate rather than deleting history. **An address shows no risk score.** It has not been screened yet, or screening could not reach a result. Do not read a blank as a pass. **Their history is empty but you know you have paid them.** The earlier payments went to an address now archived, or to a different record. ### Compliance and screening What gets screened, how to read a risk result, and what to do when a payment is flagged. #### What gets screened and when URL: https://stablerail.com/help/what-gets-screened-and-when Summary: The compliance checks that run automatically, what triggers them, and what they look at. Last updated: 2026-08-03 (v1.0) ## When you would read this When you need to explain your controls to an auditor or a bank, and when you want to understand why a particular payment was held. ## What gets screened **Every outbound payment.** When you run checks on a payment request, the destination address is screened before the payment can be signed. Nothing goes out unscreened. **Every recipient in a batch.** Each address in a batch is screened individually, and the batch takes the risk level of its riskiest member. **Incoming deposits.** Funds arriving into your wallets are screened too, so you know what you have received and from where. **Saved counterparty addresses.** Addresses are screened when you add them, and re-screened over time. See "Ongoing wallet risk monitoring". ## What the checks look at Screening combines several kinds of check into a single result: **Address risk.** Whether the destination has known associations that make it high risk, and whether it appears on a blocklist. **Policy checks.** Whether the payment satisfies your own rules: is it above your self-approval limit, does it need a supporting document, is the recipient new to you, is strict payout mode engaged. **Behavioural signals.** Whether the payment fits your organisation's normal pattern. Unusual timing, unusual size relative to your history, or a sequence of payments that looks like it is being split to stay under a limit will all raise attention. **Counterparty context.** Whether the address belongs to a counterparty you know, how long you have used it, and what you have paid them before. ## When it runs Screening runs when you select **Run checks** on a payment request, before anything can be signed. It runs again on incoming funds when they arrive. It also runs in the background against addresses you have saved. You will see a **Checking** status while it is in progress. This usually takes moments. ## What to expect The result is one of three verdicts, PASS, FLAG or BLOCK, presented as a risk dossier attached to the payment. See "Read a risk result". Everything screening produces is retained and forms part of the evidence pack for that transaction, so the result you saw at the time is reconstructable later. See "Export an evidence pack". Screening supports your compliance programme. It does not replace it, and it does not tell you what your obligations are. Those remain yours. ## Common problems and what they mean **A payment sits on "Checking".** Screening is running. If it stays there far longer than usual, contact support. **The same address passed last week and is flagged now.** Either re-screening found something new, or a behavioural check fired because this payment does not fit your pattern. **An incoming deposit is flagged.** The funds have arrived and cannot be un-received. Review the result before moving them into your main vault, and consider using quarantine addresses. See "Use a quarantine address". #### Read a risk result URL: https://stablerail.com/help/read-a-risk-result Summary: What PASS, FLAG and BLOCK mean, what the risk dossier contains, and what you can do in each case. Last updated: 2026-08-03 (v1.0) ## When you would do this Every time you approve a payment. This is the part of the screen that exists to protect you, and reading it is the job. ## The three verdicts **PASS.** The checks found nothing unusual. The payment is ready to sign. A pass is not an instruction to sign: it means nothing automated objected, and your own judgement still applies. **FLAG.** Something needs a human to look at it and say why it is acceptable. The payment is created but locked. It cannot be signed until the flag is resolved with a comment and supporting evidence. See "Resolve a flagged payment". **BLOCK.** The payment is not permitted. It cannot be signed by anyone, at any quorum, and there is no override. Reject and archive it. You will also see **CHECKING** while screening is still running. ## What the risk dossier contains Open the payment in **Operation › Signing** and read the dossier. It lists each check that ran with its own result and a description of what it found. Checks fall into groups: the destination address and its associations, your own policy rules, behavioural signals about whether this payment fits your normal pattern, and what is known about the counterparty. Alongside it, **Policy Checks** shows which of your rules applied and whether each was satisfied. ## How to read a flag A flag names the reason. Common ones include a first-time recipient above your threshold, a payment above your document threshold with nothing attached, a payment outside your usual operating hours or size, and a pattern that resembles splitting payments to stay under a limit. Read what the check actually says rather than the colour. "New recipient" on a supplier you onboarded this morning is expected. The same flag on a payment you did not initiate is not. If the explanation does not match your understanding of the payment, stop and find out why before signing. ## What to expect The dossier is stored with the transaction. It appears in the evidence pack and can be reconstructed later exactly as it was when the decision was made, along with who decided and what they wrote. A verdict applies to that payment. Creating the same payment again later can produce a different result. ## Common problems and what they mean **A blocked payment you believe is legitimate.** It still cannot be sent. Contact your account manager rather than trying to route around it. **A flag you cannot resolve.** If it is a structuring flag, the person who created the payment is not allowed to resolve it. Someone else must. **The dossier shows a check with no result.** Screening could not complete that check. Do not read a blank as a pass. **Everything is flagged.** Your thresholds may be set very low for the volume you run. Review them with an Admin. See "Set your policy thresholds". #### Resolve a flagged payment URL: https://stablerail.com/help/resolve-a-flagged-payment Summary: Clearing a flag with a comment and evidence, and the rules about who is allowed to do it. Last updated: 2026-08-03 (v1.0) ## When you would do this When a payment shows FLAG in the signing queue. It cannot be signed until the flag is resolved. ## Steps 1. Go to **Operation › Signing** and open the flagged payment. 2. Read every flag listed. There may be more than one, and all of them must be resolved. 3. Select **Resolve Flag**. 4. Write a **comment** explaining why this payment is legitimate. Write it for someone who was not there: an auditor reading it in two years with no memory of the week. 5. **Upload at least one supporting document.** This is required. An invoice, a signed contract, an approval email, a screenshot of the verification call you made. 6. Submit. 7. Once all flags are cleared, the action changes to **Sign**. ## Who is allowed to resolve a flag Anyone who can sign can normally resolve a flag. The exception is a **structuring** flag, raised when a sequence of payments looks like it is being split to stay below a limit. The person who created the payment **cannot** resolve that flag. Someone else must. The creator can still sign afterwards. Where more than one approval is required, the creator cannot be the only approver. ## What to write A good comment answers three questions: what is this payment for, how do you know the recipient is who they claim to be, and why is the thing that triggered the flag explainable. "Approved by Sarah" is not a resolution. "Invoice 4471 for the March retainer. Bank details confirmed by phone with Tom on 2 August using the number on our contract, not the one in the email. First payment to this address, hence the new recipient flag." is. ## What to expect Your comment, your documents, your identity and the timestamp are all written to the audit trail and included in the evidence pack for the transaction. They cannot be edited afterwards. Resolving a flag does not weaken the other controls. Quorum still applies, and the payment still needs its signatures. Resolving a flag is not available for a blocked payment. Blocks cannot be cleared this way. ## Common problems and what they mean **"Resolve Flag" is not offered.** You are a Requester or Viewer, or the payment is blocked rather than flagged. **You cannot resolve one particular flag.** It is a structuring flag on a payment you created. Ask a colleague. **The document will not upload.** Check the file size and format. Try a PDF. **You resolved it and it is still not signable.** Another flag remains. Check the list again. **You resolved it in error.** You cannot unwrite the comment. Cancel the payment instead, and create a new one if it should proceed. #### Ongoing wallet risk monitoring URL: https://stablerail.com/help/ongoing-wallet-risk-monitoring Summary: Why a risk score changes when you have done nothing, and what to do when one gets worse. Last updated: 2026-08-03 (v1.0) ## When you would read this When a counterparty's risk tier changes without you touching anything, or when your own vault shows a wallet risk score you did not expect. ## Why scores change on their own Screening is not a one-off check at the moment you save an address. Addresses you have saved are re-screened over time, and what is known about an address changes as the wider picture changes. An address can become higher risk because it later received funds from somewhere problematic, because it was subsequently associated with activity that screening cares about, or because information that was not available when you first added it has since emerged. Nothing you did caused it. The world moved. ## Where to see it **Governance › Counterparty** shows a risk tier on each counterparty and a risk score against each of their registered addresses. **Governance › Vaults** shows a wallet risk score on each vault, reflecting screening of the addresses that vault has interacted with. ## Steps: when a score gets worse 1. Open the counterparty and identify **which address** changed. It is often one of several. 2. Look at what you have paid to that address and when. Past payments are not undone, but you need to know the exposure. 3. Contact the counterparty through a channel you already trust and ask them to receive on a different address. 4. Add the new address, and **archive** the affected one so nobody selects it out of habit. 5. Record what you did. If a future payment to this counterparty is flagged, your comment on that flag should reference this. ## Your own wallet risk A vault can pick up a risk score from what has been sent to it, not only from what you have sent out. Unsolicited deposits from unpleasant sources affect the picture even though you did not ask for them. This is the main practical argument for **quarantine addresses**: unknown senders deposit there, you inspect, and your operating vaults stay clean. See "Use a quarantine address". ## What to expect A worsening score does not automatically block anything. It changes the risk picture, which feeds into the verdict on future payments, so payments involving that address are more likely to be flagged or blocked from now on. Changes are recorded, so you can show an auditor both what you knew and when you knew it. ## Common problems and what they mean **A long-standing supplier suddenly rates badly.** Almost always one specific address. Identify it and move them onto another. **Your treasury vault has a risk score and you only ever pay known suppliers.** Check for inbound dust deposits. See "View balances and history". **A score with no explanation you can act on.** Contact your account manager rather than guessing. ### Evidence and audit What is recorded, and how to export it for an auditor or accountant. #### What is recorded in the audit log URL: https://stablerail.com/help/what-is-recorded-in-the-audit-log Summary: The permanent record of who did what, how to search it, and how long it is kept. Last updated: 2026-08-03 (v1.0) ## When you would do this When you need to establish what happened: who approved something, when a setting changed, whether a payment was made by the person who says they made it. Everyone can read the audit log, including Viewers. ## What is recorded Every significant action, with who did it and when: - Payment requests created, cancelled, signed and executed - Flags resolved, including the comment written and the documents attached - Policy changes, quorum changes and wallet policy assignments - Team changes: invitations sent, accepted, revoked, roles changed, members removed - Wallets created and quarantine addresses created and archived - Counterparties and addresses added, archived and restored - Sign-ins, including sign-ins that used the fallback method rather than a passkey - Emergency lock engaged and released ## Steps 1. Go to **Governance › Audit log**. 2. Filter by date range, by category, by event type, or by the person who acted. 3. Search if you know roughly what you are looking for. 4. Open an entry for its full detail. 5. Export if you need it outside the app. ## What to expect The audit log is **read-only for everyone, including Admins**. There is no edit and no delete. Nobody in your organisation, and nobody at Stablerail, can alter an entry after the fact. Entries are retained for the life of your account. Archiving something does not remove it from the audit log. An archived counterparty, address or quarantine address remains fully visible in the record. If your memory of events and the audit log disagree, the audit log is the authority. ## Using it well For a specific transaction, it is usually faster to open the transaction in the Ledger and download its **evidence pack**, which assembles the audit trail for that payment along with the risk dossier, policy snapshot and documents into one file. See "Export an evidence pack". Use the audit log itself when your question spans transactions: everything one person did last month, every policy change this year, every fallback sign-in. ## Common problems and what they mean **You cannot find an event you expected.** Widen the date range first. Timestamps are recorded when the action completed, which may differ from when it was started. **An action shows a name you do not recognise.** Check your team list, including removed members. Removed members remain in the record for actions they took while active. **You want to correct an entry.** You cannot. If something was recorded with a wrong explanation, add a correcting note on the relevant transaction rather than trying to change history. #### Export an evidence pack URL: https://stablerail.com/help/export-an-evidence-pack Summary: A single file containing everything about one transaction, including a hash that proves it has not been altered. Last updated: 2026-08-03 (v1.0) ## When you would do this When an auditor, a bank, a regulator or your own board asks you to evidence a specific payment. One transaction, one file, everything in it. ## Steps 1. Go to **Operation › Ledger**. 2. Find the transaction and open it. 3. Under **Documents**, select **Evidence Pack**. 4. The pack downloads as a single compressed file. You can also download the **Receipt** on its own, or the attached **Invoice** if there is one. ## What is in the pack **Receipt.** The transaction summary. **Transaction details.** Amount, asset, network, source wallet, destination, counterparty, timestamps and the on-chain reference. **Risk dossier.** Every compliance check that ran, what each found, and the overall verdict, exactly as it stood when the decision was made. **Audit trail.** Who created the payment, who resolved any flags and what they wrote, who signed, and when each of those happened. **Policy snapshot.** The rules that were in force at the moment the payment was created, not the rules in force today. This matters: if you have since changed your thresholds, the pack still shows what applied at the time. **Documents.** Every file uploaded against the transaction, such as invoices and approval evidence. **Manifest and proof hash.** A list of every file in the pack with a fingerprint of each, plus a single hash covering the manifest. Anyone can recompute those fingerprints and confirm nothing in the pack has been altered since it was generated. ## What to expect The pack is generated when you request it, from stored records. It is not assembled from anything editable, and generating it twice gives you the same content. For a batch payment, the pack covers the batch and its recipients. Any member of your team can generate one, including Viewers. ## How to give it to an auditor Send the file as it is. Do not unpack it, rename files inside it, or re-zip it: that breaks the fingerprints and removes the thing that makes it evidence rather than a folder. If they ask how they can trust it, point them at the manifest and the proof hash. ## Common problems and what they mean **The pack has no documents folder.** Nothing was uploaded against that transaction. If your policy required a document, check whether the payment predates that policy. **The risk dossier looks thin.** The payment passed without flags, so there was less to record. **The policy snapshot does not match your current policies.** Correct. It shows what was in force at creation time. **You need many transactions at once.** Use the ledger export instead. See "Export records for your auditor or accountant". #### Export records for your auditor or accountant URL: https://stablerail.com/help/export-records-for-your-auditor Summary: Getting your transaction history, banking statements and audit trail out of the platform in a usable format. Last updated: 2026-08-03 (v1.0) ## When you would do this At period end, during an audit, or whenever your accountant asks for the underlying detail behind a set of numbers. ## Steps: export your transaction history 1. Go to **Operation › Ledger**. 2. Filter to the period and scope you need: date range, direction, vault, asset, status. 3. Select **Export**. 4. Choose the format: **PDF** for a statement someone will read, **Excel** or **CSV** for something that will be worked on. ## Steps: export banking activity 1. Go to **Operation › Banking**. 2. Open the **Statement** tab. 3. Select **Export** and choose PDF, Excel or CSV. ## Steps: export the audit log 1. Go to **Governance › Audit log**. 2. Filter to the period, category or person you need. 3. Export. ## Steps: evidence for a single transaction Use the evidence pack instead. It contains far more than a row in a spreadsheet, including the compliance checks and the rules in force at the time. See "Export an evidence pack". ## Which format for which purpose **PDF** is a fixed statement. Use it when someone needs to read and file it. **Excel** keeps the structure and is the right choice for reconciliation work. **CSV** is the plain fallback for loading into another system. ## What to expect Exports reflect the filters you have applied, so check them before you export. It is easy to send an auditor a file that silently excludes a vault. Every export contains the on-chain transaction reference for each payment. That reference is what lets your auditor verify a payment independently of anything Stablerail says, which is usually what they actually want. Earn positions can be downloaded separately from the Earn page. Records are retained for the life of your account, so an export for a prior period is always available. ## Common problems and what they mean **Your export is missing transactions you expected.** A filter is still applied. Clear them and export again. **The totals do not match your accounting system.** Check whether network fees are being treated consistently on both sides, and whether you have included internal transfers between your own vaults, which move money without being income or expenditure. **Your auditor wants proof a record has not been edited.** Give them the evidence pack for the transactions in question, which carries fingerprints for exactly this. **They ask who approved something.** The audit log export answers this across transactions. The evidence pack answers it for one. ### Fiat accounts Receiving and sending bank transfers, and converting between fiat and stablecoins. #### What your fiat account can do URL: https://stablerail.com/help/what-your-fiat-account-can-do Summary: The bank accounts available to you, what they are for, and how to get one opened. Last updated: 2026-08-03 (v1.0) ## When you would read this When you need to receive traditional bank transfers, pay a supplier who does not accept stablecoins, or move between currency and stablecoins without leaving the platform. Fiat accounts are enabled per organisation. If you do not see **Operation › Banking**, it is not switched on for you. Ask your account manager. ## What is available **A EUR operating account**, using SEPA for euro transfers. **A USD operating account**, using ACH for dollar transfers. Each account can receive incoming transfers, send outgoing transfers, hold a balance, and convert between that currency and stablecoins in your treasury. Corporate cards run on top of an open account. See "Issue a card". ## Steps: get an account opened Only an Admin can do this. 1. Go to **Operation › Banking**. 2. Complete the registration form: legal business name, registration country, registration number if you have one, and business address. The business name accepts Latin letters, digits and basic punctuation only. 3. Confirm which team members should be able to perform banking operations. Only people who have already signed in at least once can be included. 4. Select **Start KYB** and complete the business verification in the panel that opens. Have your documents ready. See "Complete your company verification". 5. Wait while the account is provisioned. This can take a few business days. 6. When the account is open, the full banking dashboard appears. The page updates itself as your status changes. You do not need to keep refreshing. ## What to expect You may be asked to accept our banking partner's terms as a separate step. Once open, each account shows its own limits, expected settlement time and applicable charges on the dashboard, under Limits, settlement and fees. Read those before your first transfer, since they differ by rail. Charges are set out in your Order Form, and your account manager can confirm what applies. Not every currency is available in every country or on every plan. ## Common problems and what they mean **"None of your team members have signed in yet."** At least one member besides you must have signed in before you can register. Ask them to log in once. **Business name rejected.** Accented characters and umlauts are not accepted. Use the closest Latin spelling. **Verification rejected, or the account suspended.** The page explains the status. Contact your account manager for the next step. There is no self-service route. **"This account already operates Banking for another organization."** Banking is bound to one organisation. Contact support. **Cards are greyed out.** Cards need an open bank account first. #### Receive funds into your fiat account URL: https://stablerail.com/help/receive-funds-into-your-fiat-account Summary: Finding your account details, giving them to a payer, and tracking what arrives. Last updated: 2026-08-03 (v1.0) ## When you would do this When a customer wants to pay you by bank transfer rather than in stablecoins, or when you are funding your account from your own bank. ## Steps 1. Go to **Operation › Banking**. 2. Select the account you want to receive into, EUR or USD. 3. Select **Account Details**. 4. Copy the details. Click any field to copy it individually, or copy the whole set at once. You can also download them as a PDF to send to a payer. 5. Send those details to whoever is paying you, along with the **reference** if one is shown. The reference is what lets the payment be matched to you. ## What you will see For a **EUR account**: IBAN, BIC, beneficiary name, bank name and bank address. For a **USD account**: account number, routing number, account type, beneficiary name, bank name and bank address. Give the payer the complete set. A transfer sent with a missing or altered beneficiary name is the most common cause of a returned payment. ## What to expect Incoming transfers appear in the **Transactions** view on your banking dashboard, and in the **Statement** tab. Settlement time depends on the rail and on the sending bank. Euro transfers over SEPA Instant normally arrive in seconds. Dollar transfers over ACH normally take one to two business days. Each account shows its own expected settlement time on the dashboard. A transfer sent late in the day, over a weekend or across a public holiday will take longer. Funds arriving into your fiat account can then be converted into stablecoins in your treasury. See "Convert between fiat and stablecoins". ## Common problems and what they mean **The payer says they sent it and nothing has arrived.** Check the expected settlement time for that rail first, then check the statement. Ask the payer for their own confirmation and the exact beneficiary details they used. **The payment was returned to the sender.** Usually the beneficiary name did not match, the reference was missing, or the sending bank queried it. Ask the payer what reason their bank gave, and resend with the exact details from the Account Details screen. **The payment is delayed for checks.** Incoming transfers can be reviewed before being credited, particularly the first one from a new payer or an unusually large amount. This is normal and out of Stablerail's hands. **The amount is lower than expected.** Intermediary banks can take charges on the way, and currency conversion by the sending bank changes the amount received. **You were given the wrong account details.** If a payer used details for a different currency account, the transfer will usually be rejected. Send them the correct set. #### Send funds from your fiat account URL: https://stablerail.com/help/send-funds-from-your-fiat-account Summary: Making a bank transfer to a counterparty, what details each rail needs, and why a payment might be returned. Last updated: 2026-08-03 (v1.0) ## When you would do this When you need to pay a supplier, employee or contractor in traditional currency. Admins and Signers can send bank transfers. Requesters and Viewers cannot. ## Steps 1. Go to **Operation › Banking**. 2. Select the account to pay from, EUR or USD, and choose **Send**. 3. **Recipient.** Pick an existing counterparty with bank details saved, or choose New Address to enter a new recipient. 4. If entering a new recipient, provide their details for the rail you are using, and choose whether they are a business or an individual. The details are saved to your counterparty list for next time. 5. **Amount.** Enter the amount. The screen shows what is available in the account. 6. **Review.** Check the recipient, the amount, the rail and the applicable charge. 7. Confirm. ## What details each rail needs **EUR over SEPA:** beneficiary name, IBAN, and optionally BIC or SWIFT and the bank name. **USD over ACH:** beneficiary name, account number, routing number, bank name, and the recipient's legal address including street, city, postal code and country. Enter the beneficiary name exactly as their bank holds it. A mismatch is the most common reason a transfer is returned. ## What to expect The transfer appears in your **Transactions** and in the **Statement** tab with a status of Pending, then Executed, or Failed. Settlement time depends on the rail. Euro transfers over SEPA Instant normally arrive in seconds. Dollar transfers over ACH normally take one to two business days. Transfers submitted outside banking hours, at weekends or on public holidays start moving on the next business day. Charges are set out in your Order Form. The review step shows the applicable charge before you confirm. ## Reversibility Once a transfer has been executed you cannot recall it from Stablerail. A receiving bank may return a payment it cannot apply, but that is the bank's decision and it can take days. Treat an executed transfer as final and check the details before confirming, not after. ## Common problems and what they mean **"Add account details."** The counterparty exists but has no bank account saved for this rail. Add one on their record. **The transfer failed.** The receiving bank rejected it. The usual causes are a beneficiary name that does not match the account, an incorrect account or routing number, or an account that does not accept that transfer type. **The transfer is returned days later.** The receiving bank accepted it, then could not apply it. The funds come back to your account, usually minus any charges taken along the way. **You cannot send.** You are a Requester or Viewer, or the balance is insufficient once charges are accounted for. **You started a transfer on one rail and switched to another.** Switching discards what you entered, because the two rails need different details. The app warns you before it does. #### Convert between fiat and stablecoins URL: https://stablerail.com/help/convert-between-fiat-and-stablecoins Summary: Moving value between your bank account and your treasury vaults in either direction. Last updated: 2026-08-03 (v1.0) ## When you would do this When money arrives as a bank transfer and you want to hold it as stablecoins, or when you hold stablecoins and need currency to pay a supplier who banks traditionally. ## Steps: fiat into stablecoins 1. Go to **Operation › Banking**. 2. Select the account holding the funds. 3. Choose **Top up**. 4. Enter the amount, and choose the treasury vault and asset to receive. 5. Review and confirm. ## Steps: stablecoins into fiat 1. Go to **Operation › Banking**. 2. Choose **Withdraw**. 3. Choose the source vault and the amount. 4. Choose the fiat account to receive the funds. 5. Review and confirm. 6. The withdrawal goes to **Operation › Signing** for approval, because it moves funds out of a treasury vault. ## What to expect A conversion into stablecoins draws on your fiat balance and credits a treasury vault. A conversion out of stablecoins draws on a vault and credits your fiat account. Because moving funds out of a treasury vault is a money movement, it is governed by your policies and your signing quorum in the same way as any payment. Expect it to need approval, and expect that to be the slow part rather than the conversion itself. The rate applied and any charges are shown before you confirm. Charges are set out in your Order Form, and your account manager can confirm what applies to your account. Balances update once each leg settles. There is a delay on the treasury side while the network confirms. ## Common problems and what they mean **The withdrawal is sitting in the signing queue.** It needs its signatures like any other payment. Chase your signers. **"Insufficient balance."** Check whether the amount plus any charge exceeds what is available, and on the treasury side whether the network fee has been reserved. **Top up is not available.** Your bank account is not open yet, or you have no balance in it. **The vault you want is not offered.** The vault does not support the asset, or is on a network not available for conversion. Pick another vault. **The amount credited is not what you expected.** Check the rate and charges shown on the review step. Conversion is not one to one between a currency and a stablecoin denominated in it. ### Cards Issuing cards, setting limits, and reviewing card spend. #### Issue a card URL: https://stablerail.com/help/issue-a-card Summary: Creating a virtual corporate card, naming it for the person who will use it, and what happens next. Last updated: 2026-08-03 (v1.0) ## When you would do this When someone on your team needs to spend on behalf of the company: subscriptions, advertising, travel, supplier accounts that only take cards. Cards are virtual and are funded from your shared treasury. There is no separate card balance to top up. ## Before you start Cards need an open bank account. If you have not activated banking, do that first. See "What your fiat account can do". Cards are also enabled per organisation and per country. If the section is not available to you, ask your account manager. ## Steps 1. Go to **Operation › Cards**. 2. Select **Issue Card**. 3. Enter the **name on card**: the person who will use it. This is what appears on the card itself. 4. Enter a **card name**: an internal label such as Marketing Ops or AWS. This is what you and your finance team will see in lists and reports, so make it descriptive. 5. Optionally set a **daily limit**. You can add or change limits later. See "Set card limits and controls". 6. Select **Issue card**. ## Assigning a card to a person A card is assigned by naming the person on it and labelling it for its purpose. Use one card per person per purpose rather than sharing a single card, so that spend is attributable and you can freeze one without disrupting everyone. Card details are revealed only to Admins. If the cardholder needs the number, an Admin retrieves it and passes it on. See "Set card limits and controls". ## What to expect A new card appears in the workspace showing **Pending** or **Awaiting activation** while it is being created, then **Active**. The workspace header shows how many cards you have out of your maximum, which is 30. Spend draws on your shared treasury. Each card transaction appears in the Card Activity view. See "View card transactions". ## Common problems and what they mean **"Activate banking first."** Cards run on your banking account. Finish activation. **"Corporate cards are not enabled for your organisation yet."** Not switched on. Contact your account manager. **"Not available for your corporation's country or plan."** Cards are not offered on your current country or plan. **"Enter a whole number of 1 or more."** The daily limit must be a whole number. Leave it empty for no daily limit. **The card is stuck on Awaiting activation.** Give it a few minutes and refresh. If it persists, contact support. **You have hit the maximum of 30 cards.** Close cards you no longer use to free up capacity. #### Set card limits and controls URL: https://stablerail.com/help/set-card-limits-and-controls Summary: Capping what a card can spend per day, per month and per transaction, and who can see card details. Last updated: 2026-08-03 (v1.0) ## When you would do this When you issue a card, when someone's responsibilities change, and after any incident that makes you want tighter control. Limits are the main control you have over a card. Set them deliberately rather than leaving everything open. ## Steps 1. Go to **Operation › Cards** and open the card. 2. Select **Set limit**. 3. Set any combination of: - **Daily**, the maximum the card can spend in a day - **Monthly**, the maximum in a calendar month - **Per transaction**, the maximum for any single purchase 4. Leave a field empty for no limit on that dimension. 5. Save. To lift a cap you have set, use **Remove limit** on that field. ## Choosing limits Set the per-transaction limit to the largest single purchase the cardholder legitimately needs. This is the control that does the most work: it caps the damage from a compromised card in one go. Set the daily limit to a normal day, not an exceptional one. A cardholder who occasionally needs more can ask. Set the monthly limit to the budget the card is meant to operate within, so the card enforces the budget rather than a report telling you about it afterwards. ## Revealing card details Card details can only be revealed by an **Admin**, using **Details** on the card. Signers, Requesters and Viewers cannot see the number, expiry or security code, whatever else they can do in the platform. Reveal details only when the cardholder actually needs them, and send them through a channel you trust. Revealing is recorded. ## What to expect Limit changes take effect immediately. A transaction that breaches a limit is declined at the point of sale. The card detail view shows daily spent against daily limit, month to date, and daily utilisation, so you can see how close a card is running to its caps before someone is embarrassed at a checkout. ## Common problems and what they mean **A cardholder's payment was declined and they are within budget.** Check all three limits, not just the one you remember setting. A single large purchase can pass the daily limit and fail the per-transaction limit. **You cannot see Set limit.** Open the card's detail view rather than acting from the list. **You cannot reveal details.** You are not an Admin. Only Admins can. **Spend appears against a card with a limit that should have stopped it.** Limits apply to new authorisations. A payment authorised before you changed the limit can still settle afterwards. #### Freeze or close a card URL: https://stablerail.com/help/freeze-or-close-a-card Summary: Stopping a card temporarily or permanently, and which one to choose. Last updated: 2026-08-03 (v1.0) ## When you would do this Freeze when a card might be compromised, when a cardholder is away, or when you want spending to stop while you investigate. Close when a card is finished with for good: the person has left, the subscription has ended, the project is over. ## Which to choose **Freeze is reversible.** The card stops working immediately and payments are declined. You can unfreeze it later and it works again. **Closing is permanent.** It cannot be undone. The card cannot be reopened and you will need to issue a new one. If you are unsure, freeze. You can always close a frozen card later. You cannot reopen a closed one. ## Steps: freeze a card 1. Go to **Operation › Cards** and open the card. 2. Select **Freeze**. 3. Confirm. Payments are declined until you unfreeze it. To reverse it, select **Unfreeze** and confirm. ## Steps: close a card 1. Open the card. 2. Select **Close card**. 3. Read the confirmation. It tells you this cannot be undone. 4. Confirm **Close permanently**. ## What to expect A frozen card shows as **Frozen** and can be unfrozen at any time. A closed card moves to the **Closed** section of the workspace. Its history stays visible: closing a card does not remove its transactions from your records or from the audit log. Transactions authorised before you froze or closed the card can still settle afterwards. Freezing stops new authorisations, it does not unwind ones already made. ## If a card is compromised 1. **Freeze it immediately.** Do this before investigating. 2. Review its recent transactions for anything you do not recognise. See "View card transactions". 3. Close it and issue a replacement rather than unfreezing it. 4. Consider whether the card details were exposed anywhere else, and check the audit log for when they were last revealed and by whom. 5. If you think the compromise is broader than one card, see "Respond to a suspected compromise". ## Common problems and what they mean **A payment went through on a frozen card.** It was authorised before the freeze and settled after it. **A recurring subscription keeps failing after you unfroze the card.** Some merchants stop retrying after repeated declines. The cardholder needs to re-enter the card with the merchant. **You closed a card by mistake.** It cannot be reopened. Issue a new one. **You cannot freeze or close.** Open the card's detail view. Check your role permits card management. #### View card transactions URL: https://stablerail.com/help/view-card-transactions Summary: Reviewing card spend across the team or for one card, and exporting it for reconciliation. Last updated: 2026-08-03 (v1.0) ## When you would do this Monthly, to review what the team spent. At period end, to reconcile card spend into your accounts. Immediately, when a card may have been compromised. ## Steps: see all card spend 1. Go to **Operation › Cards**. 2. Open the **Card Activity** tab. 3. Page through the activity, or search for a specific card or merchant. 4. Select **Export** to download it for reconciliation. ## Steps: see one card's spend 1. Go to **Operation › Cards** and open the card. 2. Its detail view shows **Recent activity** and a fuller **Transactions** list. 3. The same view shows daily spent, daily limit, month to date and daily utilisation. ## What you will see Each transaction shows the merchant, the amount, the date and the card it was made on. The card name you set when issuing is what identifies it in the list, which is why a descriptive card name is worth the effort. Card spend draws on your shared treasury, so each card transaction has both a spend amount and the corresponding movement from treasury. ## Reconciling Export the card activity and match it against your accounting system by card name and date. Card transactions can take a day or two to settle after the purchase, so a transaction that appears in one period may settle in the next. If your totals disagree by a small amount at a period boundary, check for transactions in flight before looking for a real error. ## Common problems and what they mean **A transaction you do not recognise.** Freeze the card first, then investigate. See "Freeze or close a card". **The merchant name is not the shop you visited.** Merchants often bill under a parent company or payment processor name. Check the amount and date before treating it as fraud. **An amount differs slightly from the receipt.** A foreign currency purchase is converted, and the converted amount is what lands. **A transaction is missing.** It has not settled yet. Give it a day or two. **Spend is attributed to the wrong team.** The card name is the only label carried through. Rename cards to match how you report, and issue separate cards per cost centre. **You need the underlying treasury movement.** Open the corresponding entry in **Operation › Ledger**. ### Invoicing Creating invoices, setting up recurring ones, and reconciling payment. #### Create an invoice URL: https://stablerail.com/help/create-an-invoice Summary: Billing a customer, attaching the address they should pay to, and sending it. Last updated: 2026-08-03 (v1.0) ## When you would do this When you need to bill a customer and be paid in stablecoins. Admins, Signers and Requesters can create invoices. ## Steps 1. Go to **Operation › Receive** and open the **Invoice** tab. 2. Enter an **Invoice ID**, such as INV-001. Use whatever numbering your accounting system expects. 3. Choose the **receiving wallet**. This is the address your customer will pay to, so pick the vault you want the funds in. 4. Choose the **asset** and the **chain** to receive on. 5. Choose the **counterparty**, or add a new one inline. 6. Enter the **amount**. Choose whether it is denominated in **Fiat** or **Crypto**. If fiat, pick the currency. 7. Optionally set a **due date** and a **description**. 8. Select **Preview** to check how it will look. 9. Save it: **Save & Download PDF** to send it yourself, or **Save & Send via Email** to send it from the platform. ## Attaching the receiving address The receiving wallet you choose is printed on the invoice along with the chain and asset, so your customer has everything they need to pay correctly. Choose the chain deliberately. Your customer will pay on the network shown, and a payment on the wrong network cannot be recovered. If you have billed this counterparty before, the form tells you what they paid last time and to which wallet, which is usually the right answer again. Consider using a quarantine address as the receiving wallet for a customer you do not know well. See "Use a quarantine address". ## What to expect The invoice appears in your invoice history with a status: **Draft**, **Unpaid**, **Paid**, **Matched**, **Overdue** or **Cancelled**. When the payment arrives, Stablerail attempts to match it automatically. See "Reconcile an invoice payment". Paid invoices are locked from further editing. You can cancel an invoice that has not been paid. ## Common problems and what they mean **"There are no counterparties yet."** Add the customer first, or add them inline from the invoice form. **"Amount must be greater than 0."** Enter a positive amount. **The email did not arrive.** Check the address on the counterparty record. You can always download the PDF and send it yourself. **Your customer paid a different amount.** It will not match exactly. See "Reconcile an invoice payment". **You need to change a paid invoice.** You cannot. Issue a credit note or a corrected invoice through your accounting process. #### Set up a recurring invoice URL: https://stablerail.com/help/set-up-a-recurring-invoice Summary: Billing the same customer on a schedule, with automatic follow-ups when they are late. Last updated: 2026-08-03 (v1.0) ## When you would do this For retainers, subscriptions, rent, and anything else you bill on the same terms every period. Set it up once instead of creating an invoice each time. ## Steps 1. Go to **Operation › Receive** and open the **Recurrent** tab. 2. Select **New Recurrent Invoice**. 3. Enter an **Invoice ID** pattern, such as REC-001. 4. Choose the **receiving wallet**, the **asset** and the **chain**. 5. Choose the **counterparty** and the **email** the invoice should go to. 6. Enter the **amount** and the payment terms. 7. Choose the **frequency**: Weekly, Bi-weekly or Monthly. 8. Set the **day of week** or **day of month** the invoice should be issued on. 9. Turn on **Auto Follow-ups** if you want reminders sent automatically when an invoice becomes overdue. 10. Save. ## What to expect Stablerail generates each invoice automatically on the schedule you set and emails it to the address on the counterparty. Each generated invoice behaves like any other: it appears in your invoice history, it can be paid, and it is matched to the incoming payment when it arrives. With auto follow-ups on, reminders are sent at one, three and seven days after the due date passes without payment. They stop once the invoice is paid. You can **pause or cancel** a recurring schedule at any time. Pausing stops new invoices and reminders without deleting the invoices already issued. ## Choosing a day For monthly billing, pick a day that exists in every month. A schedule set to the 31st behaves unpredictably in February. For weekly and bi-weekly billing, pick a weekday. Invoices issued on a Saturday sit unread until Monday, which effectively shortens your payment terms. ## Common problems and what they mean **An invoice was not generated.** Check whether the schedule is paused, and whether the counterparty still has a valid email address. **Reminders keep going out after they paid.** The payment has not been matched to the invoice, so it is still recorded as unpaid. See "Reconcile an invoice payment". **The customer says they are getting duplicates.** You may have both a recurring schedule and a manually created invoice for the same period. Cancel one. **You need to change the amount.** Cancel the schedule and create a new one. Invoices already issued are unaffected. **Your customer wants to pay on a different chain.** Cancel and recreate on the chain they want. Do not tell them to pay a different address than the one printed on their invoice. #### Reconcile an invoice payment URL: https://stablerail.com/help/reconcile-an-invoice-payment Summary: How incoming payments are matched to invoices, and how to match or unmatch one yourself. Last updated: 2026-08-03 (v1.0) ## When you would do this When a customer has paid but the invoice still shows as unpaid, or when a payment has been matched to the wrong invoice. ## How matching works When funds arrive, Stablerail looks for an open invoice that fits: the same counterparty, amount, asset and chain. An exact match is linked automatically and the invoice becomes **Matched**. Anything that is not an exact match is left for you. It is deliberately not guessed at, because a wrong automatic match is worse than none: it closes an invoice that is still owed and marks a payment as settling something it did not. ## Steps: match a payment yourself 1. Go to **Operation › Receive** and find the invoice in your invoice history. 2. Select the option to match a transaction. 3. Review the candidate payments. These are confirmed incoming payments that are not yet matched to anything. 4. Check each candidate: the amount, the sending wallet and the transaction reference. Candidates that fit precisely are marked **Exact**. 5. Select **Match**. If a candidate does not fit precisely you will see a warning explaining why, such as **Amount differs by a percentage** or **Sender wallet not on file for this counterparty**. Read the warning, satisfy yourself it is genuinely the right payment, then choose **Match anyway**. ## Steps: unmatch a payment 1. Open the invoice. 2. Select **Unmatch**. 3. Optionally record a reason, such as "wrong invoice picked". 4. Confirm. The invoice returns to unpaid and the payment becomes available to match against something else. ## What to expect Matching is a bookkeeping link. It does not move funds and it does not change what happened on the network. The payment is yours either way. Matching and unmatching are recorded in the audit log, including the reason you gave. Invoice status flows from Draft to Unpaid, then to Paid or Matched, with Overdue if the due date passes first, and Cancelled if you cancel it. ## Common problems and what they mean **"No unmatched confirmed payments available."** The payment has not arrived yet, has not confirmed yet, or is already matched to another invoice. Check the ledger. **"Sender wallet not on file for this counterparty."** They paid from an address you have not saved against them. Verify it is really them, then save the address on their record so it is recognised next time. **"Amount differs."** They underpaid, overpaid, or a fee was deducted in transit. Decide whether to accept it as settlement before matching anyway. **Two invoices for the same amount.** Match by transaction reference and date rather than amount. **They paid on a different chain from the invoice.** The payment still arrived if the address was yours. Match it manually. ### Earn Putting idle funds to work, and moving them back out. #### Put idle funds to work with Earn URL: https://stablerail.com/help/put-idle-funds-to-work-with-earn Summary: Depositing treasury balances into yield vaults, withdrawing them again, and what to understand before you do. Last updated: 2026-08-03 (v1.0) ## When you would do this When you are holding stablecoin balances you do not need immediately and want them to generate a return rather than sitting idle. Earn is optional. Whether your team can use it, and whether a single signer can approve it, is controlled by your policies. ## Before you start Earn is not a deposit account and it is not guaranteed. Returns vary, are not fixed, and can change at any time. Value can fall as well as rise. Funds remain yours throughout. Stablerail does not take custody of them. Deposits and withdrawals are money movements, so they go through your normal approval controls. ## Steps: deposit 1. Go to **Operation › Earn**. 2. Choose the **asset** you want to deposit. 3. Review the vaults available for it. Each shows its current rate, size, risk tier (Conservative, Balanced or Aggressive) and any minimum timelock on withdrawals. 4. Open the vault you want and select **Deposit**. 5. Choose the **source wallet** and enter the **amount**, or use MAX. 6. Review the projected earnings shown, remembering they are projections based on the current rate and not a promise. 7. Submit. 8. Approve it in **Operation › Signing**. ## Steps: withdraw 1. Go to **Operation › Earn** and find the position under **Your positions**. 2. Select **Withdraw**. 3. Enter the amount and submit. 4. Approve it in **Operation › Signing**. ## What to expect Your positions view shows total deposited, current value, total earned and the blended rate across your positions, and you can download it as CSV. Rates are variable and update continuously. The rate you saw when depositing is not the rate you will earn throughout. Some vaults apply a **timelock**, a minimum period before a withdrawal completes. This is shown before you deposit. Check it against when you might need the money. Withdrawals can also be affected by available liquidity in the vault, so a very large withdrawal may not complete instantly. ## Common problems and what they mean **"No vaults registered for this asset yet."** Nothing is available for that asset. Choose another, or ask your Admin. **"Pick a treasury wallet first."** Choose the source wallet before entering an amount. **Your deposit is not showing.** It is in the signing queue awaiting approval. Nothing moves until it is signed. **Your earned figure went down.** Value moves with the underlying position. It is not a fixed accrual. **A withdrawal is taking longer than expected.** Check the vault's timelock, and whether the vault currently has liquidity available. **Earn requires full quorum every time.** Earn self-approval is switched off in your policies. An Admin can change it. See "Set your policy thresholds". ### Policies The approval rules that govern every payment, and how to change them safely. #### What the policy engine controls URL: https://stablerail.com/help/what-the-policy-engine-controls Summary: The rules that are applied to every payment automatically, and where each one bites. Last updated: 2026-08-03 (v1.0) ## When you would read this Before you change anything in **Governance › Policies**, and when you want to understand why a particular payment was held. Everyone can view your policies. Only an Admin can change them. ## How policies are applied Every payment request is checked against your policies automatically when it is created. There is no route that skips them, and no per-payment override. A policy decides two things: whether a payment can proceed on one signature or needs your full quorum, and whether it needs anything extra from a human before it can be signed. ## What you can control **Document requirement threshold.** Payments above this amount require an uploaded invoice or supporting document before they can be signed. **New recipient flag threshold.** First-time recipients above this amount are flagged for additional review. **External payment self-approval.** Below this limit one signer can create and send a payment alone. Above it, your quorum applies. This can also be switched off entirely, so that every external payment needs at least one additional signer. **Swap self-approval.** A separate per-transaction limit for swaps, which can also be switched off so all swaps need quorum. **Earn self-approval.** Whether a single signer can deposit to and withdraw from Earn vaults, or whether full quorum is required. **Internal transfers.** Whether moves between your own vaults are auto-approved, and up to what amount. **Strict payout mode.** If a batch payout contains any address that is new to you, the whole batch is flagged for Admin review. **Solo operator safeguards.** If you are the only signer, require dual verification, both authenticator code and passkey, when paying a first-time address. **Native token self-approval limits.** Separate per-coin limits for native coins such as ETH, BTC and SOL, entered in units of that coin. Until you enable and configure these, native coin payments require full quorum regardless of the limits set elsewhere. ## Starting templates Two templates give you a sensible starting point: **Standard**, which is efficiency focused, and **Strict**, which is control focused. Pick one and then adjust individual controls. The **Policy Summary** panel restates your current settings in plain language, and is worth reading back before you publish. ## What to expect Policies are applied at the moment a payment request is created, against the rules in force at that instant. The rules that applied are stored with the transaction and appear in its evidence pack, so a decision can always be reconstructed against the rules of the day rather than today's rules. #### Set your policy thresholds URL: https://stablerail.com/help/set-your-policy-thresholds Summary: Choosing the numbers behind your rules, and how to pick them for the way your company actually pays. Last updated: 2026-08-03 (v1.0) ## When you would do this At setup, when your payment volumes change, after an incident, or when your team complains that everything is flagged. Only an Admin can change policies. ## Steps 1. Go to **Governance › Policies**. 2. Choose a starting template, **Standard** or **Strict**, or start from your current settings. 3. Work through the controls on the External Payments and Internal tabs, setting each threshold. 4. If you use native coins, enable **Native Token Self-Approval Limits** and set a limit per coin. You can prefill these from your currency limits and then adjust. 5. Read the **Policy Summary** panel. It restates everything in plain language. 6. Select **Publish Changes**. 7. Sign the queued policy update in **Operation › Signing**. ## How to choose your numbers **Document threshold.** Set it at the point where you would expect a paper trail anyway. Too low and your team uploads the same document repeatedly for routine payments, which trains everyone to treat evidence as a formality. Too high and your largest payments have nothing behind them. **New recipient threshold.** Set it low. Paying someone for the first time is where nearly all payment fraud happens, and the cost of a flag is a few minutes. **External self-approval limit.** Set it at the amount you would be comfortable with a single trusted person sending without anyone else looking, on their worst day, on a phone, in a hurry. That number is usually lower than the first one people suggest. **Swap and internal limits.** These can reasonably be higher than external payments, because funds stay under your control. They are not zero risk, but a mistake is recoverable in a way an external payment is not. **Native coin limits.** Entered in units of the coin, not in currency. A limit that looks small in coin terms may be large in value, and the value moves. ## What to expect Publishing does not take effect immediately. It queues a policy update that requires signatures, then applies. Changes apply to payments created after they take effect. Payments already in the queue keep the rules they were created under. If your team says everything is flagged, that is information. Either your thresholds are wrong for your volumes, or your payment patterns are genuinely irregular. Find out which before loosening anything. ## Common problems and what they mean **You cannot edit anything.** You are not an Admin. **Your change has not applied.** It is waiting in the signing queue. **Native coin payments still need quorum.** Native limits are not enabled, or not set for that coin. **"Live exchange rates unavailable."** The prefill from currency limits cannot be calculated. Enter the coin amounts manually. #### Edit policies safely URL: https://stablerail.com/help/edit-policies-safely Summary: How a policy change takes effect, what happens to payments already in flight, and how to avoid loosening controls by accident. Last updated: 2026-08-03 (v1.0) ## When you would do this Any time you are about to change a rule that governs money movement. Read this first if you are loosening anything. ## How a change takes effect A policy change is not a setting that saves when you click. 1. You edit the controls and select **Publish Changes**. 2. The change is queued as a governance item in **Operation › Signing**. 3. It requires signatures, exactly like a payment. 4. Once signed, it takes effect. Until it is signed, nothing has changed. If you publish a change and walk away, your old rules are still running. ## What happens to payments already in flight Policies are evaluated **when a payment request is created**, against the rules in force at that moment. That means: - Payments already in the signing queue keep the rules they were created under. Tightening a policy does not retrospectively block them, and loosening one does not release them. - A payment created after the change takes effect uses the new rules. - A payment that is stuck because of a rule will **not** be released by changing that rule. Cancel it and create it again under the new policy. The rules that applied are stored with each transaction and appear in its evidence pack, so an auditor sees the rules of the day, not today's rules. ## Loosening a control safely 1. Change one thing at a time. If several controls move at once and something goes wrong, you will not know which one did it. 2. Read the **Policy Summary** panel before publishing. It restates your settings in plain language and is the easiest place to spot a control you did not mean to touch. 3. Write down why, outside the platform, so the next person understands the intent. 4. Watch the next few days of payments. If flags disappear entirely, you have probably gone too far. ## Removing a policy from a wallet You can detach a policy from an individual vault. This disables transaction governance and self-approval controls on that vault, which is a significant loosening. It is queued for signatures like any other change. Do it deliberately, not to work around a blocked payment. ## What to expect Every policy change is recorded in the audit log with who made it, who signed it, and when. This is one of the first things an auditor looks at. ## Common problems and what they mean **Your change is not applying.** It is unsigned in the signing queue. **A stuck payment did not unstick after you changed the rule.** Expected. Cancel and recreate it. **You cannot publish.** You are not an Admin. **You published something you regret.** Publish a corrective change and sign it. You cannot delete the record of the first one. ### Security and recovery Protecting your account, losing a device, and what to do if you suspect compromise. #### Protect your account URL: https://stablerail.com/help/protect-your-account Summary: The habits and settings that actually reduce your risk, and the emergency lock. Last updated: 2026-08-03 (v1.0) ## When you would read this When you set up, and periodically as a check. Most losses in this kind of product come from ordinary process failures rather than anything exotic. ## Protect your own access - Register a passkey on each device you use regularly, so you are not relying on the fallback method every time. - Store your recovery key offline, and not in the same password manager you sign in from. - Never share a sign-in code with anyone, including anyone claiming to be from Stablerail. We will never ask for one. - Sign out on shared machines rather than relying on the idle timeout. ## Protect the organisation **Keep your quorum above one for meaningful amounts.** A second reader is the control that catches what the first one misses. A quorum of one means one compromised account is enough. **Set your new-recipient threshold low.** First payments to new addresses are where fraud lands. **Pay from saved counterparties, never from a pasted address.** And never copy an address out of your transaction history. **Verify payment detail changes by phone**, on a number you already hold, before adding a new address. See "Manage counterparty addresses safely". **Review the audit log periodically.** Look for fallback sign-ins, policy changes you do not recognise, and members you did not expect. **Remove people promptly when they leave**, and check your quorum still works afterwards. **Use quarantine addresses** for unknown senders so your operating vaults stay clean. ## The emergency lock An Admin can engage an **emergency lock** from **Settings › Security**. It halts payments immediately across the organisation. To engage it you type **LOCK** to confirm. To release it you type **UNLOCK**. Use it the moment you suspect something is wrong. It is reversible, it costs you an hour of inconvenience, and it is far cheaper than the alternative. Do not wait until you have established what happened. ## What to expect None of these controls prevent a determined insider with legitimate access from making a legitimate-looking payment. What they do is ensure it takes more than one person, and that everything is recorded. Engaging and releasing the lock are both recorded in the audit log. ## Common problems and what they mean **Your team finds the controls slow.** That is the trade-off you configured. Review the thresholds rather than switching controls off. **You cannot engage the lock.** You are not an Admin. **Payments are all failing and nobody knows why.** Check whether the lock is engaged. #### Recover access to your account URL: https://stablerail.com/help/recover-access-to-your-account Summary: What to do when a device or a signer is lost, and why we cannot recover keys for you. Last updated: 2026-08-03 (v1.0) ## When you would do this When someone cannot sign in: a lost or replaced phone, a lost laptop, a signer who has left without handing over, or a broken authenticator. ## Why we cannot simply reset it Stablerail cannot move your funds, and that is the same fact as not being able to hand someone access to them. There is no master key we hold. If we could restore signing capability on request, then anyone who could impersonate you convincingly could ask us to. This means recovery is a procedure with checks, not a self-service reset. There is deliberately no "forgot password" email that restores access to money. ## Steps 1. **If you think the device was stolen rather than lost**, treat it as a compromise first. See "Respond to a suspected compromise". 2. **Contact support.** Recovery runs through a support procedure. Start it as early as possible, because it involves verification and that takes time. 3. **Check your quorum still works in the meantime.** If the person who lost access was one of two required signers, your payments are blocked until this is resolved. An Admin can adjust the threshold or add another signer as an interim measure, which is itself a governed change that must be signed by whoever remains. 4. **Do not create workaround accounts.** Inviting someone under a personal email to get moving again creates a much bigger problem than the one you are solving. ## If a signer has left the company 1. Remove them from **Settings › Team** promptly. 2. Check your signing threshold still makes sense with one fewer signer, and adjust it if not. 3. Review the audit log for their recent activity. 4. If they held cards, freeze or close them. See "Freeze or close a card". ## What to expect Recovery takes as long as verification takes. Plan for it to be days rather than minutes, and keep enough signers that losing one does not stop the company. Your funds are not at risk while this is happening. They are where they were. What is affected is your ability to move them. ## How to make this easier before it happens - Keep more signers than your threshold requires. A 2 of 3 quorum survives losing one person. A 2 of 2 does not. - Make sure every signer has stored their recovery key offline. - Do not concentrate Admin and every signing capability in one person. - Register passkeys on more than one device where practical. ## Common problems and what they mean **"Ask an Admin to reset your security."** An Admin can help with some access issues, but not with recovering signing capability. That is the support procedure. **You are the only Admin and you have lost access.** Contact support immediately. This is the scenario the advice above exists to prevent. **You can sign in but cannot sign payments.** Your passkey or authenticator is registered but your signing capability is not available on this device. Contact support. #### Respond to a suspected compromise URL: https://stablerail.com/help/respond-to-a-suspected-compromise Summary: What to do first when something looks wrong, in the order that limits the damage. Last updated: 2026-08-03 (v1.0) ## When you would do this When you see a payment nobody admits to creating, a counterparty address you do not recognise, a team member you did not invite, a card transaction from nowhere, or a colleague reporting a phishing email that someone may have acted on. Act on suspicion. Do not wait until you have established what happened. ## Steps 1. **Engage the emergency lock.** An Admin does this from **Settings › Security**, typing **LOCK** to confirm. It halts payments immediately. It is reversible and it costs you an hour. Do this first, before investigating. 2. **Contact support.** Tell us what you have seen and that you have locked the account. 3. **Cancel anything in flight.** Anything in the signing queue that is not fully signed can be cancelled. Nothing has moved yet. 4. **Freeze cards** that could be involved. See "Freeze or close a card". 5. **Check the audit log** for the period in question: sign-ins including fallback sign-ins, payments created, counterparty addresses added or changed, policy changes, and team changes. 6. **Check your team list** for members or pending invitations you did not authorise, and revoke them. 7. **Check counterparty addresses** for anything added recently, especially on suppliers you pay regularly. Archive anything you cannot account for. 8. **Have affected people re-secure their access** through support. See "Recover access to your account". 9. **Release the lock only when you understand what happened** and have removed the cause. ## What you cannot undo A payment that has been broadcast cannot be recalled. If funds have already left, the lock stops further loss but does not recover what has gone. See "What can and cannot be reversed". This is why the lock comes first and the investigation second. ## The most common real scenarios **A changed supplier address.** Someone acted on an email asking to update payment details. Check every counterparty address added recently, and see "Manage counterparty addresses safely". **A compromised email account.** Payment instructions arrived from a genuine address belonging to someone whose mailbox was taken over. Verify by phone, always. **A shared or reused sign-in.** Check the audit log for sign-ins that do not fit the person's working pattern. **A card number leaked.** Freeze, review, close and reissue. ## What to expect Everything you do during the response is recorded, which is what you will need afterwards for your insurer, your bank or your regulator. Stablerail cannot reverse blockchain payments and cannot recover sent funds. We can help you understand what happened and secure what remains. ### Troubleshooting and FAQ Common problems and what they mean. #### Troubleshooting and FAQ URL: https://stablerail.com/help/troubleshooting-and-faq Summary: Quick answers to the questions that come up most often, with links to the full article for each. Last updated: 2026-08-03 (v1.0) ## Signing in **I cannot sign in.** Check you are using the email your account was created with, and that your phone's clock is set automatically. If your passkey is not recognised on this device, use the email and authenticator fallback. See "Sign in and secure your account". **I keep getting signed out.** You are signed out after 15 minutes of inactivity, and after a longer fixed period regardless. **I joined but see no organisation.** You signed in with a different email from the one your invitation was sent to. Ask your Admin to revoke and re-invite. **I lost my phone.** See "Recover access to your account". ## Payments **The Sign button is missing.** You are a Requester or Viewer, the payment is blocked, or you have already signed it. **My payment needs another approver.** It is above your self-approval limit. See "Understand self-approval limits". **My payment is flagged.** Open it, resolve the flag with a comment and a document, then sign. See "Resolve a flagged payment". **My payment is blocked.** It cannot be sent by anyone. Reject and archive it, and contact your account manager if you believe it is legitimate. **Nothing happened after I signed.** You were not the last required signer. **I sent to the wrong network.** The funds cannot be recovered. See "What can and cannot be reversed". **Can I cancel a payment?** Yes, until the last required signature. After that, no. See "What can and cannot be reversed". ## Balances **My deposit has not appeared.** Wait for network confirmation, then refresh balances. If you can see it on a block explorer, use Import transaction on the Ledger. See "View balances and history". **My balance dropped by more than I sent.** The network fee comes out on top of the amount. See "Network fees and gas sponsorship". **I have tiny balances I did not ask for.** Unsolicited dust, sometimes used in address-poisoning attempts. Never copy an address from your transaction history. ## Access and features **I cannot see Banking, Cards, or Earn.** They are enabled per organisation. Ask your Admin or your account manager. **I cannot edit policies or invite people.** Only Admins can. **I cannot reveal card details.** Only Admins can. **Everything is failing at once.** Check whether the emergency lock is engaged, on Settings › Security. ## Money questions **What does it cost?** Charges are set out in your Order Form. Your account manager can confirm what applies. **Can Stablerail move our funds?** No. See "How self-custody works here". **Can you reverse a payment for us?** No. Nobody can, once it is broadcast. **Can you recover our keys?** No. Recovery runs through a support procedure and restores access, not keys. See "Recover access to your account". ## Getting help For roles, policies, limits and feature access, ask your Admin. They control all of it. For anything else, including a payment that appears genuinely stuck, a suspected compromise, or account recovery, contact support. Have the transaction reference ready.