Acceptable Use Policy

1. Purpose and Scope

BillingMart provides software for professional billing, invoicing, client management, and card/bank payments. This Acceptable Use Policy ("AUP") applies to all users, workspace owners, developers using our REST APIs, and automated systems interfacing through our Model Context Protocol (MCP) server.

Violation of this policy may result in immediate suspension or termination of your workspace and reporting to payment networks or law enforcement authorities.

2. Financial Integrity and Anti-Fraud

You must not use BillingMart to engage in deceptive, fraudulent, or illegal financial practices. Specifically, you may not:

• Generate fictitious invoices, phantom billing records, or fabricated tax documents.
• Conduct unauthorized charges or credit card testing on our payment endpoints or hosted pay pages.
• Operate as an unlicensed money transmitter, payment aggregator, or currency exchange.
• Launder money or obscure the genuine origin, recipient, or beneficial owner of funds.
• Attempt to tamper with server-derived arithmetic, taxes, line-item totals, or ledger balances.

3. Anti-Spam and Verified Contacts

BillingMart’s delivery architecture relies strictly on verified contacts. You agree that:

• You will only send invoices, estimates, and payment requests to recipients who have an existing commercial or contractual relationship with your business.
• You will never upload, import, or target purchased, rented, scraped, or harvested contact lists.
• All customer email communications must comply with the CAN-SPAM Act, CASL, and GDPR transparency requirements.
• All SMS delivery and phone verification must comply with TCPA regulations and CTIA guidelines, respecting STOP and opt-out requests immediately.

4. AI Assistant and MCP Server Conduct

Additionally, you agree not to:

• Inject malicious instructions or adversarial prompt injections into invoice line items, customer notes, or template descriptions designed to hijack connected AI assistants.
• Circumvent token rate limits or abuse MCP server connections with automated polling loops.
• Attempt to query cross-tenant records through the MCP server or REST API.

5. System Security and Reverse Engineering

You may not:

• Probe, scan, or test the vulnerability of our pay page origin (pay.billingmart.com), API host, or console without express authorization under a signed testing agreement.
• Attempt to bypass or weaken our Content Security Policy, origin isolation, or database security rules.
• Decompile, disassemble, or reverse engineer any part of the BillingMart source code or compiled assets.
• Share API keys or administrative accounts across multiple organizations or unauthorized third parties.

6. Restricted and Prohibited Activities

BillingMart cannot be used in connection with goods or services prohibited by our banking and gateway partners (including TranzPay), such as:

• Unlawful gambling, gaming, or sweepstakes.
• Counterfeit, infringing, or unauthorized merchandise.
• Predatory lending, pyramid schemes, or deceptive get-rich-quick offers.
• Products or services that violate applicable sanctions or export control laws.

7. Monitoring, Investigation, and Suspension

We reserve the right to investigate suspected violations of this policy. While an investigation is underway, we may temporarily restrict your ability to dispatch new invoices or access our API.

In accordance with our platform invariants, even in the event of an account restriction, previously generated customer invoices remain intact and visible to prevent harm to unrelated third-party clients.

8. Reporting Violations

If you suspect that a business on BillingMart is sending fraudulent invoices, conducting deceptive billing, or violating this policy, please report it immediately to abuse@billingmart.com or write to security@billingmart.com.