> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sardine.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# How Sardine Bills
> This guide explains Sardine's billing process and how Sardine bills for different products and services
## Invoicing timing and procedures
In most cases, Sardine generates invoices and billing receipts on the first business day after the close of a calendar month.
We email invoices to the billing contact provided in the original contract. If you do not receive an invoice, please contact us at [billing@sardine.ai](mailto:billing@sardine.ai) to confirm we have the correct email address.
## Product specific billing
Monthly recurring charges are those that are billed to your account at regular monthly intervals and predetermined amounts. Sardine bills monthly recurring charges for the following products, some of which may not apply to your plan with Sardine:
* Platform fees (dashboard, rule editor, case management, and AI-fraud scoring)
* Premium support
* Monthly prepaid credit plans
* 3rd party dashboard fees, such as Coinbase Tracer
Usage charges are those that are billed based not only on the number of API calls made, but also takes into account the data posted in your API calls. The following table indicates the default methods for how Sardine determines whether to consider a call for billing.
**Keep in mind, this may not reflect custom structures that are set up in agreements.**
| Use Case | API Calls | How we charge |
| ---------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Fraud** | | |
| Device Intelligence & Behavior Biometrics | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API (recommended) and [/devices](/guides/api-reference/device/get-device-information) API | Per API or per Monthly Active User. |
| Identity fraud (US & non-US):
1. Email enrichment and AI score.
2. Phone enrichment and AI score
3.Address verification | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API, when emailAddress, phone, or address is provided | Per unique email, phone, or address for a customer id. |
| Bank funding fraud | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API, when transaction object has bank\_accountNumber and bank\_routingNumber | Per transaction and/or per bank account. |
| Card fraud | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API when transaction object has payment method type = card | Per transaction and/or per card hash |
| Stolen/Unauthorized card use detection (for card issuers) | [/issuing/risks](/guides/api-reference/issuing-risk/realtime-risk-check-for-creditdebit-card-authorization-requests-for-card-issuers) API | Per card authorization attempt. |
| **Compliance** | | |
| Sanctions (SDN, OFAC), PEP & Adverse Media, Screening & Monitoring | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API when the checkpoint includes ‘AML’ and relevant customer data points (first name, last name, country, and dob *optional*) are provided. The Sanctions feature must also be enabled by Sardine. | Per unique dataset of first name, last name, country, and dob. |
| SSN Verification with Synthetic ID Detection | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API when taxid is provided | Per unique tax id for a given customer id |
| Documentary KYC with Selfie-Liveness Detection | [ /identity-documents](/guides/api-reference/document-verification/document-verification-using-web-link) API
SDK: [/identity-documents/tokens](/guides/api-reference/document-verification/document-verification-token-to-be-used-in-native-sdks) | Per verification attempt (Billing is based on API success, not whether approve or decline is returned). |
| AML Transaction Monitoring for fiat | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API when checkpoint includes ‘AML’ and a transaction object is present with a payment method type other than crypto. | Per transaction |
| AML Transaction Monitoring for crypto, incl. Coinbase Analytics | [/customers](/guides/api-reference/customer/evaluate-customer-sessiontransaction-risk) API when checkpoint includes ‘AML’ and a transaction object is present with payment method type is crypto or recipient payment method type is crypto. | Per transaction |
## How usage charges are counted
* **Per MAU:** We charge for each unique `customer_id` during the month. If calls are made to either our devices API without a `userIdHash` or Customers API without a `customer_id`, we charge for the `device_id` (we consider these anonymous users).
* **Per Transaction:** We charge for every unique `transaction_id`, excluding API calls where configuration flags are set to bypass data processing.
* **Per Email, Phone, Bank Account, etc.:** We charge once for each unique email address, phone number, or bank account per `transaction_id` per year observed in API calls to the `/customers` endpoint.