Crypto Processing Terms

Last updated: 2026-10-03 Version: 1.0 Status: Advance notice Effective: New products and features: first use on or after 7 October 2026; existing services: 10 November 2026, subject to the notice period below

For newly available products and features, this edition applies when you first choose to use the relevant service and accept its terms, on or after 7 October 2026. The product must actually be launched and available to you. For changes to services you already use, this edition applies from 10 November 2026, but never earlier than 30 days after we notify you of the changes, or a later date required by applicable law. Until then, the previous conditions continue for those existing services. Accepting in advance does not shorten that transition. Publication and acceptance do not make a product available or establish regulatory permission.

These terms govern Swaps Crypto Processing, including crypto invoices, Payment Links and scheduled invoices that use the Tempo payment contract route. The service is provided by Supa Labs OÜ, registry code 17399414, Oru tn 2, Tallinn 10127, Estonia ("Swaps"). These terms supplement the Terms of Service and Payment Link Terms and control for this route. They describe the actual payment mechanism, not a regulatory licence or an exemption from applicable law.

1. What the service does

A Merchant requests an amount of supported stablecoins and selects an eligible settlement wallet. A Payer chooses an offered route, reviews the payment details and authorises payment from their own wallet or service. Swaps provides the invoice, deposit instructions, monitoring, transaction records and contract-release automation.

The Merchant supplies the goods or services, sets the invoice amount and is responsible for the underlying sale. That sale is between the Merchant and Payer; Swaps supplies the software and performs the payment-route functions described here. Swaps does not guarantee the Merchant's performance, provide escrow adjudication, or insure the payment. This division of roles does not exclude Swaps' responsibility for its own service. Bank settlement and conversion through Bridge are separate routes governed by the relevant product and provider terms.

Availability is limited to the assets, networks, holders and routes enabled for the particular request. This document does not make a planned or unavailable feature available.

2. The contract payment path

For each payment attempt, instructions identify a computed contract address on Tempo. That address is bound to the Merchant destination, Swaps fee destination and Merchant amount before funding, even if the contract has not yet been deployed. Deploying the contract at that address fixes those same values; it does not allow a different recipient to be substituted. A successful release transfers the fixed Merchant amount to that Merchant wallet and the remaining balance of the released token to the Swaps fee wallet, subject to the fee and excess-payment distinction in sections 4 and 6.

The Payer authorises the funding transfer through their wallet or source service. The later contract release is a separate transaction and does not require another signature from the Payer. Swaps operates a monitoring service and uses its own transaction-signing infrastructure to deploy the contract if needed and pay for and trigger release. Release is also callable by others; the caller cannot replace the fixed destinations or Merchant amount. Swaps does not hold the Merchant's or Payer's wallet signing key. The contract has no administrator mechanism that lets Swaps rewrite those fixed values or retrieve an arbitrary deposit.

These restrictions do not eliminate software, token or network risk. Distribution requires successful on-chain execution. The contract does not decide commercial disputes, verify goods, or hold funds until a Payer approves delivery.

3. Paying from another network

Where offered, a cross-network route uses Relay infrastructure, including a deposit address or deposit transaction, protocol contracts and a solver that delivers the destination asset. Funds leave the source wallet before they arrive at the Tempo payment contract. This creates third-party infrastructure, liquidity, execution and recovery dependencies in addition to the Tempo contract risk.

Relay's Terms of Use apply to its functionality. A cross-network quote, source deposit or successful source transaction alone does not establish that the Merchant received payment. Completion requires the destination leg and the contract distribution.

A source-network refund address, where requested, has a different purpose from the Merchant's Tempo settlement wallet. It must be valid for the stated source network and controlled by the person entitled to receive the return. Do not provide a Tempo-only wallet address as an address on another network merely because its format is accepted. Swaps cannot guarantee that a failed route has an automatic refund or that an exchange withdrawal address can receive a return.

Use a source wallet whose signing and recovery access you control unless the payment instructions expressly support another source. An exchange withdrawal can leave you unable to sign a recovery request or receive a return. Acceptance of a refund address's format does not prove ownership, access or entitlement, and that address need not be the immediate on-chain sender. Relay returns and returns of excess already received by Swaps are separate processes.

4. Fees and amounts

The standard Swaps fee is 1% of the invoice amount, paid by the Payer on top. The Merchant's invoice amount, Swaps fee and total requested are shown in the payment instructions. Provider, cross-network and network costs are separate where applicable. A 1% Swaps fee is not a promise that total payment costs are 1%.

The contract transfers the fixed Merchant amount and the entire remaining released balance to the fee wallet. On an exact payment, that remainder is the disclosed Swaps fee. If more is paid, it can include excess beyond the disclosed fee. That excess is not an additional agreed fee; section 6 explains its treatment.

Use the exact asset and amount shown. Stablecoins can lose value, have different issuer or redemption terms, and trade at different prices. A dollar-denominated request does not guarantee redemption for a dollar or a fixed exchange rate between tokens.

5. Short, late and unmatched payments

A payment below the requested total may be reported as underpaid and need a top-up before Swaps completes it. Do not assume that a published tolerance for a bank route also applies here.

If the contract holds less than its fixed Merchant amount in the token to be released, release fails. The current contract has no general withdrawal or refund function for that balance. A correctly instructed top-up may allow release; without it, the amount can remain inaccessible. Contact support before adding funds, particularly if the token, network or attempt does not match.

Payments sent after an attempt closes, to the wrong network, in an unsupported token, or without enough evidence to match the attempt are investigated separately. An unmatched deposit is not automatically released or refunded. Swaps may be unable to recover it. A transaction hash or an invoice status alone is not evidence that a recovery is possible.

6. Overpayments and return requests

If an eligible payment exceeds its requested total, the Merchant still receives the fixed invoice amount and the excess can reach the Swaps fee wallet alongside the agreed fee. Swaps records the overpayment separately from the agreed fee and accepts requests to return the verified excess. Returns are not automatic.

For a matched direct Tempo payment from a wallet controlled by the Payer, the return path is to the verified originating Tempo address after reconciliation, entitlement and applicable compliance checks. Swaps will not replace that destination solely on an unverified instruction. If an exchange, custodian, intermediary or cross-network route was the sender, support must establish an appropriate return path with the relevant parties; the immediate on-chain sender may not be the Payer and may not credit a return.

This excess-return process is separate from a refund of the Merchant's sale and from a Relay source-network return. It does not promise recovery of a balance still locked in a contract or held by another party. Any necessary return costs will be explained before a return is arranged, subject to applicable law. Nothing here permits Swaps to keep excess funds as an undisclosed fee or removes a mandatory restitution right.

7. Merchant refunds and cancellation

The Merchant remains responsible for lawful cancellations, refunds, taxes and consumer remedies for the underlying sale. A Merchant returning a settled crypto payment must authorise a separate transfer from a wallet it controls, using a verified destination. The original transaction cannot be reversed by Swaps.

Cancelling or expiring a payment page does not alter a deployed contract or reverse a deposit. Once payment has started, ask support about its state before changing the request or paying again. An unavailable refund button does not remove rights against the Merchant.

8. Scheduled invoices

A schedule issues a separate invoice for each due period. Each invoice requires a manual payment by the Payer. No recurring debit authority, standing wallet approval or automatic withdrawal is created by this feature.

Pausing or cancelling a schedule stops future issuance as described in the product; it does not cancel previously issued invoices or the underlying subscription contract. Unpaid invoices can remain payable and do not automatically terminate the schedule. There is no implied proration, automatic debt collection or refund.

9. Wallet security and service restrictions

The Merchant is responsible for maintaining signing access to its settlement wallet. If it is a Swaps Wallet, the Wallet Service Terms apply, including passkey, domain binding and loss-of-access risks. A wallet address can receive funds even if its owner has lost the ability to sign.

Swaps can decline new requests, restrict an interface or stop its own automated processing under the Acceptable Use Policy, Sanctions Policy and Limits & Enforcement. Such a restriction does not give Swaps a contract override, stop a third party from calling a permissionless function, or freeze assets in a self-controlled wallet. Token issuers and third-party route operators may have their own controls.

10. Risk information and data

Smart contracts, monitoring services, networks, solvers and stablecoin issuers can fail. A claim that a payment was tested does not mean it was independently audited or insured. Do not assume that an independent security audit exists unless an applicable report is expressly identified. Read the Risk Disclosure.

A risk signal or address label is probabilistic, can be wrong and does not certify a Payer, Merchant or transaction as lawful or safe. Screening does not replace verification required for another product or route. Challenges to a signal can be submitted to legal@swaps.app.

The Privacy Policy covers invoice, account, wallet, receipt and transaction information. A Merchant must lawfully provide customer data and explain its use. Blockchain transactions are public and cannot be erased by Swaps.

11. Liability, changes and contact

Availability, changes, complaints, dispute resolution and liability follow the Terms of Service, including mandatory consumer rights and responsibility that cannot lawfully be excluded. These terms do not create a separate liability cap, promise a recovery outcome, or excuse Swaps from responsibility for its own breach.

For a payment issue use support.swaps.app. Legal contact: legal@swaps.app.