Payment Link and Invoice Terms

Last updated: 2026-10-03 Version: 2.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 Payment Links and invoices, provided by Supa Labs OÜ, registry code 17399414, Oru tn 2, Tallinn 10127, Estonia ("Swaps"). They supplement the Terms of Service. These terms control for Payment Links; the Crypto Processing Terms control the specific crypto contract route they describe. Mandatory consumer rights remain unaffected.

1. Requests for payment and the parties

A Merchant creates a request identifying the amount, goods or services and settlement destination, and shares a payment page with a Payer. "Merchant" means the individual or business requesting payment, where the product permits that holder and purpose. "Payer" means the person making that payment. An invoice or payment page does not itself prove a debt, a completed payment, the Merchant's identity, or delivery of goods or services.

The Merchant and Payer remain responsible for their underlying sale or other obligation. Swaps supplies the request, routing and status interface and performs the route-specific functions below. Swaps is not the seller of the Merchant's goods, the Merchant's agent for resolving sales disputes, or an escrow adjudicator. Swaps remains responsible for its own service as required by the Terms and applicable law.

2. How payment reaches the Merchant

Provider route. For a route using Bridge, Swaps submits the authorised instruction and displays the provider's deposit instructions and events. The applicable Bridge entity and its partners receive, convert where applicable, and deliver funds under the Bridge terms presented during onboarding. The entity and services depend on the holder and jurisdiction. A provider's authorisation covers its services; it does not confer an authorisation on Swaps.

Crypto contract route. An enabled crypto payment can instead fund a computed address on Tempo that is bound to the Merchant destination, Swaps fee destination and invoice amount before funding. The contract may be deployed after funds arrive. The Payer authorises funding through their wallet or source service; Swaps creates the instructions, monitors deposits and can sign a separate transaction to deploy the contract and trigger its fixed distribution. Release is also callable by others, without changing the bound destinations or Merchant amount. The Merchant receives the invoice amount and the remainder goes to a Swaps fee wallet. An optional cross-network leg uses third-party infrastructure before that distribution. This is not a Bridge payment merely because it appears on the same payment page. Read the Crypto Processing Terms, particularly the underpayment, overpayment and recovery provisions.

On a Relay route, the source transfer, destination delivery and payment-contract distribution are separate steps. A source transaction alone does not establish payment to the Merchant. The immediate sender on Tempo may be a solver rather than the Payer and must not be treated as a verified refund destination.

Use only the asset, network, amount, destination and reference shown for your current payment attempt. A bank account number, wallet address or reference copied from another attempt may not work. Display of an address does not mean that all assets, networks or senders are accepted there.

3. Merchant eligibility and responsibilities

A Merchant must have authority to request payment, a Swaps account in good standing, and access to the selected route. Provider routes require the relevant holder's verification, acceptance of provider terms and any required endorsements. Preparing a draft does not satisfy these requirements. Crypto-only collection into a supported wallet has different requirements; it does not by itself grant access to bank collection or conversion.

The Merchant must:

• accurately describe the goods, services, amount, taxes, customer and payment purpose;
• have authority to use the settlement destination and check it before activation;
• provide legally required seller information, cancellation and refund terms to the Payer;
• comply with tax, invoicing, consumer and privacy obligations for the underlying transaction;
• avoid putting unnecessary personal or sensitive information on a shared payment page.

Anyone with a public payment link may be able to view its permitted payment details. Share it only with its intended audience. Swaps may require changes to misleading or prohibited requests.

4. Payer responsibilities and availability

Opening a link does not normally require a Swaps account. It does not establish that the Payer has passed identity verification. Depending on the route, a Payer may need to provide declarations, complete checks, use an eligible source account or wallet, and comply with provider terms. Do not misstate whether you are an individual or business or who owns the funds.

Available methods and limits depend on the Merchant's holder type, jurisdiction, verification, currency, amount and destination, and on the Payer and route. Refer to the current payment instructions and Limits & Enforcement. There is no universal individual limit or promise that every advertised network or currency works for every request.

Check that you recognise the Merchant and the underlying purchase before paying. Never pay an invoice merely because a third party claims Swaps has verified its legitimacy.

5. Fees, currency and payment status

The payment page or approval screen identifies the amount requested, any Swaps fee and the applicable funding instructions. On the Tempo crypto contract route, the standard Swaps fee is 1% of the invoice amount, paid on top by the Payer. Provider-route fees and who bears them follow the disclosed route. Provider, bank, network and conversion costs may also apply; the Swaps fee is not a statement of total cost.

A currency equivalent or estimated arrival amount is indicative until the applicable transaction is confirmed. Send the funding amount in the specified asset and currency, including disclosed fees; do not convert an invoice amount yourself and assume it will reconcile.

Creation, activation, a QR code, a sent transaction, or an observed deposit does not prove final settlement. Status follows the relevant provider and blockchain evidence and can change if a provider reports a return or an error. A receipt records the payment information available to Swaps; it does not certify the Merchant's delivery or tax treatment.

6. Underpayment, excess payments and mistakes

There is no single tolerance that applies to every route. A short payment may remain incomplete, require an additional payment, or enter provider review. Provider deposits may be returned under that provider's procedures. Tempo contract payments follow the Crypto Processing Terms; a contract below its release threshold has no general refund function.

Do not send a second full payment to remedy a delay. Check the existing payment first and use updated top-up instructions only where provided. Payments to an expired or cancelled request, duplicate payments, unsupported assets, incorrect references and unmatched deposits need investigation and may not be recoverable.

An overpayment does not increase the price of the Merchant's sale or the agreed Swaps fee. On the Tempo contract route, excess can reach the Swaps fee wallet alongside the disclosed fee; that receipt does not make the excess an additional fee. Excess funds must be identified by route and destination; the fact that a payment is marked paid does not mean an excess has been returned.

7. Cancellation, returns and disputes

Cancelling a request stops its normal use in the Service; it does not reverse a bank transfer or blockchain transaction and cannot disable an already deployed contract. Cancellation may be unavailable while funds are in flight.

A refund for goods or services is the Merchant's responsibility under its agreement with the Payer and applicable law. Provider returns follow provider procedures. For crypto contract payments, a Merchant refund is a separate authorised transfer; excess reaching a Swaps fee wallet is handled under the specific excess-return process in the Crypto Processing Terms. Swaps cannot claw back funds in another person's wallet.

Contact in-product support or support.swaps.app for payment tracing. We can inspect the records available to us and coordinate with the relevant party. Assistance is not a promise that a transfer can be cancelled, recovered or returned by a particular date. A payment dispute does not remove any mandatory right against Swaps for its own service.

8. Scheduled invoices

Where scheduled invoices are available, each period creates a separate payment request that the Payer pays manually. Creating or accepting a schedule does not authorise a debit from a bank account or wallet and does not store a payment mandate.

Pausing stops new scheduled invoices while paused. Cancelling stops future issuance. Neither action automatically cancels invoices already issued, refunds a paid invoice, or cancels the underlying commercial agreement. Existing open invoices can remain payable. Non-payment does not automatically end the schedule. The Merchant must manage its own contract cancellation and collection obligations and avoid issuing duplicate requests.

9. Controls and data

The Acceptable Use Policy, Sanctions Policy and AML Statement apply. Swaps can restrict interface access or new instructions; providers can independently review or restrict transfers. A restriction does not give Swaps control over a Payer's or Merchant's private keys or permit an arbitrary change to contract destinations.

The Privacy Policy explains processing of Merchant, Payer, invoice, wallet and transaction data. A Merchant must have a lawful basis for sharing customer information and provide appropriate notices. Blockchain records cannot be deleted by removing the invoice from the interface.

10. General terms and contact

The Terms of Service govern changes, availability, liability, complaints and disputes, including all mandatory consumer protections. These terms do not introduce a separate liability cap or waive rights arising from our own breach.

Contact: legal@swaps.app