Payment Link Terms

Last updated: 2026-06-18 Version: 1.0

These terms govern the Swaps Payment Links product. They supplement the Terms of Service, and in the event of conflict between these terms and the main Terms for matters specific to Payment Links, these terms control.

By creating, activating, sharing, or accepting payment through a Payment Link, you agree to these terms. They are offered by Supa Labs OÜ, an Estonian private limited company with registry code 17399414 and registered office at Oru tn 2, Tallinn 10127, Estonia ("Swaps", "we", "us", "our").

1. What Payment Links is — and is not

1.1 — Product description. A Payment Link lets a Swaps user (the "Merchant") create a public request for payment — technically an invoice consisting of a client, one or more line items, and a settlement destination. The Merchant shares a public page (swaps.app/pay/<token>), where the Merchant's customer (the "Payer") sees who is requesting payment, for what, and how much, and then pushes payment using a rail convenient to them.

1.2 — Interface only. Payment Links is a technical and commercial interface. Swaps presents the request, collects the Payer's chosen rail, and instructs the regulated Provider to create and settle the transfer on the Merchant's behalf. Swaps does not itself move, exchange, or settle money.

1.3 — Not a counterparty. Swaps is not the seller, the buyer, the payee, the payer, the merchant of record, or any other party to the payment. The Payer transacts with the Merchant. Settlement is executed by the Provider under the Provider's own authorisations and terms. Swaps is not a party to that contract and does not guarantee the underlying commercial transaction between Payer and Merchant.

1.4 — Not a payment service or e-money product. Payment Links is not a payment account, wallet, e-money product, or escrow service. Swaps does not hold balances, does not issue payment instruments, and does not provide regulated payment services. See the Terms of Service §1.3-1.4.

2. The parties

• "Merchant" — the Swaps user who creates and activates a Payment Link to request payment. The Merchant is the payee and the counterparty to the Payer.
• "Payer" — the Merchant's customer who opens the public link and pushes payment. The Payer does not need a Swaps Account and is not identity-verified by Swaps.
• "Provider" — Bridge, the regulated provider that creates and settles the transfer on the Merchant's behalf, directly to the Merchant's settlement destination. Bridge operates under its own authorisations and its own terms of service.

3. No custody, no counterparty

3.1 — Non-custodial. Swaps never receives, holds, transmits, or takes custody of any funds at any point in a Payment Link transaction, and is never a destination for funds. The Payer's payment is created and settled by the Provider and delivered directly to the Merchant's settlement destination. See the Terms of Service §1.3.

3.2 — Settlement is the Provider's act. The transfer that moves value from the Payer to the Merchant is created and executed by the Provider under the Provider's authorisations. Deposit matching is performed by the Provider using a unique reference code attached to each request — not by sender name. The Payer must include the reference exactly as shown; payments sent without the correct reference may be delayed, unmatched, or returned by the Provider.

3.3 — Swaps is not a party to the payment. Consistent with the Terms of Service §1.2, Swaps is not a counterparty to any Payment Link transaction and does not warrant that the Payer will pay, that the Merchant will deliver, or that any underlying goods or services conform to what was agreed between them.

4. Merchant eligibility and Provider terms

4.1 — Business KYB requirement. By default, a Payment Link can be activated only by a Merchant who is a Provider-verified (Bridge KYB) business customer in approved status. A Merchant who has not completed Bridge business verification, or whose Provider status is not approved, cannot activate a link.

4.2 — Acceptance of Provider terms. Before a link can be activated, the Merchant must have accepted the Provider's (Bridge's) own terms of service. Those terms — not these — govern the Merchant's relationship with the Provider, including settlement timing, supported destinations, fees the Provider charges, and the Provider's compliance, refund, and dispute handling.

4.3 — Limited individual / P2P availability. A limited individual or peer-to-peer path may be made available behind a feature flag in some circumstances, but it is not the default and its availability is determined and gated by the Provider. Where offered, it is subject to the Provider's rules and to the Payer limits in §6.

4.4 — Merchant responsibilities. The Merchant is responsible for the accuracy of each link (client, line items, amount, settlement destination), for the lawfulness of what is being sold, for its own tax obligations, and for keeping its settlement destination (crypto wallet address or bank account) correct and under its control. Swaps does not verify that a settlement destination belongs to the Merchant.

5. Payer terms

5.1 — No Swaps verification. The Payer is not registered with, KYC'd by, or otherwise identity-verified by Swaps. The Payer does not enter into an Account relationship with Swaps by paying a link.

5.2 — Self-declaration. The Payer self-declares on the public page whether they are paying as a business or as an individual. Swaps does not independently verify that declaration. The Provider applies its own region, KYC, and screening rules at the moment of transfer.

5.3 — Individual cap. Where the Payer pays as an individual, the payment is capped at the equivalent of USD $4,000 per payment. Business Payers and further limits are subject to the Provider's rules.

5.4 — Provider-determined rails and limits. The payment rails available to a Payer, and any further limits, holds, or eligibility conditions, are determined by the Provider and may change at any time without notice. Availability is not guaranteed for any particular country, rail, or amount, and is subject to the Provider's region and compliance rules at transfer time.

5.5 — Payer obligations. The Payer is responsible for paying the correct amount to the correct destination using the correct reference code, and for satisfying the Provider's requirements for the rail they choose. Disputes about the underlying goods or services are between the Payer and the Merchant (see §9).

6. Fees

6.1 — Swaps fee. Swaps earns a fee of up to 1% on a settled Payment Link transaction, collected as the Provider's developer fee on the transfer. The exact rate is disclosed to the Merchant at activation and may vary.

6.2 — Provider fees. The Provider may charge its own fees for creating and settling the transfer. Those fees are governed by the Provider's terms (see §4.2), are separate from the Swaps fee, and are not set or collected by Swaps.

6.3 — No fee on the binding amount. Swaps does not set the binding price of the underlying transaction between Payer and Merchant. The amount payable, the currencies, and the settlement outcome are determined by the Merchant's request and by the Provider's execution.

7. Settlement and rails

7.1 — Payer-side rails (pay-in). Depending on Provider availability, a Payer may push payment via, among others: USD (ACH, Wire, FedNow), EUR (SEPA), GBP (Faster Payments), BRL (PIX), and MXN (SPEI). Available rails are Provider-determined and may change (see §5.4).

7.2 — Merchant settlement (pay-out). The Provider settles directly to the Merchant's chosen settlement destination — either crypto (USDC on supported chains) or fiat to the Merchant's own external bank account. Supported settlement currencies and chains are limited and Provider-determined.

7.3 — Underpayment tolerance. Because amounts can vary slightly across rails and conversions, a Payment Link may be treated as paid where the received amount falls within an underpayment tolerance of approximately 1%. Amounts outside the Provider's tolerance may be treated as unpaid, partially paid, or returned, in accordance with the Provider's handling. See also Limits & Enforcement §4.

7.4 — No guarantee of settlement. Swaps does not warrant that any payment will be initiated, matched, completed, or settled within any particular time. Settlement timing and success are determined by the Provider, the chosen rail, and the Payer's bank or wallet.

8. Refunds — Swaps does not refund

8.1 — Swaps never received the money. Because Swaps never receives, holds, or takes custody of Payment Link funds (§3.1), Swaps does not issue refunds for Payment Link payments. Swaps cannot reverse, return, or claw back a payment it never held.

8.2 — Refunds are between Payer, Merchant, and Provider. Any refund, return, credit, or adjustment arising from a Payment Link transaction is a matter between the Payer, the Merchant, and the Provider, under the Merchant's own refund policy and the Provider's terms. The Swaps fee under §6.1 relates to a settled transfer and is not a fund Swaps can return on the Provider's behalf.

9. Disputes and failed or underpaid transactions

9.1 — Disputes route to the Provider and the Merchant. Chargebacks, reversals, recalls, and disputes about whether, how much, or to whom a payment was made are handled by the Provider under the Provider's rules; disputes about the underlying goods or services are between the Payer and the Merchant. Swaps is not an arbiter of these disputes and does not adjudicate, hold, or release funds.

9.2 — Failed transactions. If a payment fails (wrong reference, expired or cancelled request, unsupported rail, Provider outage, or the Payer's bank rejection), Swaps does not refund, because Swaps did not receive payment. Any return of funds is performed by the Provider that received them. Consistent with the Terms of Service §5.4.

9.3 — Underpaid or overpaid transactions. Payments outside the tolerance in §7.3 are handled by the Provider. Swaps does not top up, hold, or return the difference.

9.4 — How Swaps assists. Where reasonable and lawful, Swaps will share the information it holds about a Payment Link (such as the request, the reference code, and timestamps) to help the Merchant or Payer reach the Provider. See Limits & Enforcement §4 for how to request this assistance and what we can and cannot do.

10. Prohibited use

Payment Links must not be used for any purpose prohibited by the Acceptable Use Policy, by the Provider's terms, or by applicable law. This includes, without limitation, using a link to collect payment for unlawful goods or services, to facilitate fraud or money laundering, to misrepresent who is requesting payment or for what, or to evade sanctions, KYC, or anti-fraud controls. We may deactivate any link and suspend any Merchant for breach, in line with Limits & Enforcement. The Provider may independently decline, reverse, or block any transfer under its own controls.

11. AML and sanctions

11.1 — Provider performs KYC/KYB and execution. Swaps does not custody or execute Payment Link transfers. The Provider performs customer due diligence (KYC/KYB), transaction screening, and execution under its own authorisations and AML programme. See the AML statement.

11.2 — Swaps AML role. Swaps maintains its own AML programme and assists the Provider as required under the Bridge Developer Agreement, without at any point holding or moving funds. Swaps does not provide regulated financial services through Payment Links.

11.3 — Sanctions. Payment Links are subject to the Sanctions policy. Merchants and Payers must not be located in, resident in, nationals of, or subject to comprehensive sanctions of, any restricted jurisdiction, and must not appear on any applicable sanctions list. The Provider performs sanctions screening at transfer time; Swaps enforces perimeter controls as described in the Terms of Service §3.3-3.4.

12. Privacy

Personal data processed in connection with Payment Links — including the Merchant's account data, the client and line-item details on a request, and limited data the Payer provides to complete payment — is governed by the Privacy Policy. The Payer's payment is created and settled by the Provider, which processes the Payer's data under the Provider's own privacy notice. The Merchant is responsible for handling its customers' data lawfully, including any data it enters into a Payment Link.

13. No warranty

Payment Links is provided "as is" and "as available". Swaps does not warrant that any link will be available, that any payment will be initiated, matched, completed, or settled, or that any rail, currency, country, or limit shown will remain available. Provider availability, rails, currencies, and limits can change without notice. See the Terms of Service §15.

14. Limitation of liability

Swaps' liability in connection with Payment Links is limited as set out in the Terms of Service §16, including the cumulative liability cap in §16.1, the excluded-damages provisions in §16.2, and the statutory carveouts in §16.3. Nothing in these terms restates, raises, or lowers that cap. Without limiting that section, Swaps is not liable for the acts or omissions of any Provider, Merchant, or Payer, for the underlying commercial transaction, or for any failure, delay, reversal, or non-settlement of a payment executed by the Provider.

15. Changes

We may modify these terms, the Payment Links product, the supported rails and currencies, the Merchant eligibility rules, the Payer limits, and the fee — including by reflecting changes the Provider makes — by updating this page. Material changes that reduce Merchant or Payer rights take effect on the date stated when we publish them. Provider-determined rails, currencies, and limits may change at any time without notice, as stated above.

16. Disputes about these terms

Disputes about these terms — as distinct from disputes about an underlying payment, which are handled under §9 — are first addressed by emailing legal@swaps.app. If not resolved within 30 calendar days, the dispute resolution and consumer-carveout provisions in the Terms of Service §21-22 apply.

Contact: legal@swaps.app