Skip to main content
grid
Last Updated: June 27, 2026

Amboss Payments Acceptable Use Policy and Know-Your-Business Policy

1. Purpose and Scope

This Amboss Payments Acceptable Use Policy and Know-Your-Business Policy (this “Policy”) governs Customer's access to and use of the Amboss Payments service, including the Amboss Payments Platform and any associated APIs, tooling, and infrastructure (collectively, “Amboss Payments”). This Policy is incorporated by reference into the Amboss Technologies, Inc. General Terms and Conditions for All Services (the “Terms”) and constitutes a Policy under those Terms. Capitalized terms used but not defined in this Policy have the meanings given in the Terms.

This Policy applies to Amboss Technologies, Inc. (“Amboss”, “we”, “us”) and to each Customer who registers for or uses Amboss Payments. By completing the Amboss Payments onboarding flow, including by checking the “I agree to the Acceptable Use Policy” box, Customer agrees to be bound by this Policy. If Customer does not agree, Customer may not access or use Amboss Payments.

2. Acceptable Use

2.1 Lawfulness Standard

Amboss Payments is provided for lawful purposes only. Customer may use Amboss Payments solely for business activities that are licensed (where a license is required) and lawful under all Applicable Laws in each jurisdiction where Customer conducts business, operates its Amboss Payments Node, or serves end users. Customer is solely responsible for determining whether its activities are lawful in each applicable jurisdiction and for obtaining and maintaining all required licenses, registrations, and authorizations.

Amboss does not apply sector-based restrictions beyond the lawfulness standard above. Whether Customer may use Amboss Payments in connection with a particular industry or business activity depends on whether that activity is lawful and appropriately licensed in the relevant jurisdiction(s), not on whether the activity falls within a named category. Customer is responsible for conducting this analysis for its own business.

2.2 Prohibited Uses

Customer may not use Amboss Payments to:

  • (a) facilitate, enable, or process payments in connection with any activity that is unlawful under Applicable Laws in the jurisdiction where such activity occurs or where the relevant end user is located, regardless of whether Customer's own use of Amboss Payments is otherwise lawful;
  • (b) route or process payments on behalf of any person or entity that Customer knows or reasonably should know is subject to sanctions or is otherwise designated on any Sanctions List (as defined in the Terms);
  • (c) circumvent, evade, or assist any other person in circumventing or evading sanctions, export controls, anti-money laundering laws, or any other Applicable Laws;
  • (d) process payments in connection with terrorist financing, money laundering, or any activity designated as a financial crime under Applicable Laws;
  • (e) provide payment services to end users in sanctioned jurisdictions or to sanctioned persons, even if Customer's own account is not directly sanctioned;
  • (f) misrepresent Customer's business activity, jurisdiction of operation, or end-user base to Amboss during onboarding or at any time during the use of Amboss Payments; or
  • (g) use Amboss Payments in any manner that violates the Terms, this Policy, or any other applicable Policy provided by Amboss.

2.3 End-User Responsibility

Amboss Payments is a self-custodial infrastructure service provided to businesses and developers (B2B). Amboss does not have a direct relationship with Customer's end users and does not perform KYC/AML screening on those end users. If Customer uses Amboss Payments to process payments on behalf of end users (i.e., Customer is an intermediary rather than the final merchant or payee), Customer is solely responsible for:

  • (a) implementing and maintaining a KYC/AML program applicable to those end users that satisfies all Applicable Laws in the relevant jurisdiction(s);
  • (b) screening end users against applicable Sanctions Lists;
  • (c) filing any suspicious activity reports (SARs) or equivalent regulatory filings required under Applicable Laws with respect to end-user transactions; and
  • (d) ensuring that end-user activities processed through Customer's Amboss Payments Node comply with this Policy.

By accepting this Policy, Customer acknowledges and agrees that Amboss Payments is optimized for self-custody and that, where Customer processes payments on behalf of end users, Customer is solely responsible for performing any Know-Your-Customer and anti-money-laundering screening required under Applicable Laws with respect to those end users.

2.4 Travel Rule

Amboss is not a Virtual Asset Service Provider (VASP) and does not, as of the Effective Date, have direct obligations under the FATF Travel Rule or FinCEN's travel rule regulations. Amboss will collect, process, or transmit identifying information in connection with transactions only to the minimum extent required by Applicable Law. To the extent Customer is itself a VASP or otherwise subject to travel rule obligations under Applicable Laws, Customer is solely responsible for complying with those obligations, including any requirements to collect, transmit, or retain transaction counterparty information. Amboss will cooperate with Customer's reasonable written requests for information in Amboss's possession that is necessary for Customer's compliance with travel rule obligations, subject to Amboss's own legal constraints and privacy obligations.

3. Geographic Restrictions and Sanctions Compliance

Customer may not use Amboss Payments in any manner that violates applicable sanctions or export control laws, including those administered by the U.S. Office of Foreign Assets Control (OFAC), the United Nations Security Council, the European Union or its Member States, or other applicable governmental authorities. Customer represents and warrants that neither Customer nor any party that owns or controls Customer or Customer's financial institutions is subject to sanctions or designated on any Sanctions List.

Amboss uses Reflex, its internal blockchain analytics and transaction screening tool, as part of its compliance program. Reflex produces a record of each screening review. Amboss may also use third-party compliance service providers for supplementary KYC/KYB screening of Customers, as well as other third-party data sources for business verification purposes. Amboss reserves the right to screen Customer's onboarding information and ongoing activity through these tools and to take any action permitted under the Terms based on the results of such screening, including suspension or termination of access to Amboss Payments.

The geographic restrictions applicable to Amboss Payments are the same as those applicable to the Amboss Services generally as set forth in the Terms. Customer is solely responsible for determining whether its use of Amboss Payments is permitted in each jurisdiction where Customer operates or serves end users.

4. Know-Your-Business (KYB) Policy

4.1 KYB Requirement

All Customers must complete Amboss's KYB process before receiving production access to Amboss Payments. The KYB process is designed to verify the identity and lawfulness of Customer's business. Submission of false or misleading information in the KYB process is a material breach of this Policy and the Terms and will result in immediate termination of access to Amboss Payments.

4.2 Required KYB Information

Customer must provide the following information during the Amboss Payments onboarding flow:

  • (a) Business / Legal Name: The full legal name of Customer's business entity.
  • (b) Website or App URL: The URL of Customer's primary business website or application. Amboss may use this URL for automated business verification and screening purposes.
  • (c) Country of Operation: The primary country in which Customer conducts business.
  • (d) Business Description: A brief description of Customer's business activity and the intended use of Amboss Payments (200 characters maximum).
  • (e) Expected Payment Volume: Customer's estimated monthly Gross Payment Volume through Amboss Payments. This information is used for risk classification and account configuration.
  • (f) Use Case Questionnaire: Customer must answer questions identifying whether Customer processes payments on behalf of end users or operates as a self-custody merchant accepting payments for its own account. Responses to this questionnaire determine Customer's end-user KYC obligations under Section 2.3 of this Policy.
  • (g) License Evidence for Regulated Activities: If Customer's business activity is in a regulated or high-risk sector — including, without limitation, gambling or iGaming, adult content or services, money services, currency exchange or money transmission, firearms, or (to the extent permitted under Section 2.1) cannabis-related businesses — Customer must, upon request and in any event before receiving production access, provide documentary evidence of each license, registration, or authorization required to conduct that activity lawfully in each applicable jurisdiction. Amboss may condition, suspend, or deny production access pending its satisfactory verification of such evidence, and any such Customer will be subject to manual review under Section 4.4(b).

4.3 Automated Screening

Amboss will conduct automated screening of the information provided in the KYB process, including business name screening against applicable Sanctions Lists and automated verification of the business URL. Amboss uses Reflex, its internal blockchain analytics and screening tool, which produces a record of each screening review. Amboss may also use third-party compliance service providers for supplementary KYB/KYC screening of Customers, as well as other third-party data sources for business verification purposes. Amboss collects and processes KYB information only to the extent reasonably necessary for compliance with Applicable Laws and for risk management purposes.

4.4 Approval and Access

Customer access to Amboss Payments following KYB submission is determined as follows:

  • (a) Auto-Approval. Customers that are determined to be low or medium risk based on automated KYB screening will be granted production access to Amboss Payments, including the ability to generate API keys and connect an Amboss Payments Node. Customers in this category include, without limitation, self-custody merchants that accept payments for their own account and are operating in non-sanctioned jurisdictions with no adverse screening results.
  • (b) Manual Review. Customers that are flagged for manual review based on automated screening results — including Customers whose business activity involves processing payments on behalf of end users, Customers whose business activity is in a regulated or high-risk sector as described in Section 4.2(g) (whose production access is further conditioned on Amboss's satisfactory verification of the license evidence required under that Section), Customers in higher-risk jurisdictions, or Customers with ambiguous use cases — will receive limited sandbox access pending completion of Amboss's manual review process. Amboss will use reasonable efforts to complete manual review promptly and will notify Customer by email upon completion.
  • (c) Denial. Amboss reserves the right to deny access to Amboss Payments to any Customer whose KYB submission indicates a violation of this Policy, the Terms, or Applicable Laws, or for any other reason in Amboss's reasonable discretion.

4.5 Ongoing Obligations

The KYB obligation is ongoing. Customer must notify Amboss promptly and in any event within ten (10) business days if any of the following occur: (a) a material change in Customer's business activity, ownership, or jurisdiction of operation; (b) any change in Customer's licensing status or any revocation, suspension, or expiration of a license required for Customer's use of Amboss Payments; (c) Customer becomes subject to sanctions or is designated on any Sanctions List; or (d) Customer's expected payment volume increases materially above the volume disclosed in the KYB process. Amboss may request updated KYB information at any time, and Customer must provide such information within ten (10) business days of request.

4.6 Data Retention

Amboss will retain KYB records and related compliance documentation collected in connection with the Amboss Payments onboarding process for the period required under Applicable Law and Amboss's agreements with its compliance service providers. Amboss will retain such records for no less than five (5) years from the date of collection or the date Customer's account is closed, whichever is later, consistent with record-keeping standards under the Bank Secrecy Act as applied to Amboss's compliance program. This retention obligation applies to Amboss's own KYB records. Customer is solely responsible for its own record-keeping obligations under Applicable Laws, including any BSA or equivalent obligations that apply to Customer in its own capacity as an MSB, VASP, or otherwise. Amboss's handling of KYB data is further described in the Amboss Privacy Policy.

5. Onboarding Acknowledgments

As part of completing the Amboss Payments onboarding flow, Customer must affirmatively confirm each of the following by checking the applicable box:

  • (a) “I agree to the Amboss Terms and Conditions.” Customer has read, understands, and agrees to the Terms.
  • (b) “I agree to the Amboss Payments Acceptable Use Policy and KYB Policy.” Customer has read, understands, and agrees to this Policy.
  • (c) “I understand that Amboss Payments is a fully self-custodial service.” Customer acknowledges that Amboss does not hold, control, or have access to Customer's Digital Assets or private keys at any time, and that Customer is solely responsible for the custody and security of its Amboss Payments Node and associated Digital Assets.

6. Enforcement

Amboss reserves the right to investigate any suspected violation of this Policy. In the event of a confirmed or suspected violation, Amboss may, without limiting any other rights or remedies under the Terms:

  • (a) suspend Customer's access to Amboss Payments immediately and without prior notice if Amboss determines that Customer's continued access poses a risk to Amboss, its vendors, or any third party;
  • (b) terminate Customer's access to Amboss Payments upon notice in accordance with the Terms;
  • (c) report Customer's information and activity to applicable regulatory or law enforcement authorities to the extent required by Applicable Laws or in Amboss's reasonable judgment; and
  • (d) take any other action reasonably necessary to protect Amboss, its affiliates, its vendors, and third parties from harm arising from Customer's violation of this Policy.

Amboss's failure to enforce any provision of this Policy in any instance does not constitute a waiver of Amboss's right to enforce the same provision or any other provision in the future.

7. Changes to This Policy

Amboss may update this Policy from time to time. Amboss will provide Customer with prior written notice of any material changes by posting the updated Policy on the Amboss Payments Platform and/or notifying Customer by email. Customer's continued use of Amboss Payments after the effective date of any updated Policy constitutes acceptance of the updated Policy. If Customer does not agree to the updated Policy, Customer must cease using Amboss Payments before the effective date of the changes.

8. Contact

Questions about this Policy or about Customer's compliance obligations in connection with Amboss Payments should be directed to Amboss Technologies, Inc. at [email protected].

blur