How Sardine Bills

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 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 API (recommended) and /devices 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 API, when emailAddress, phone, or address is provided	Per unique email, phone, or address for a customer id.
Bank funding fraud	/customers API, when transaction object has bank_accountNumber and bank_routingNumber	Per transaction and/or per bank account.
Card fraud	/customers 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 API	Per card authorization attempt.
Compliance
Sanctions (SDN, OFAC), PEP & Adverse Media, Screening & Monitoring	/customers 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 API when taxid is provided	Per unique tax id for a given customer id
Documentary KYC with Selfie-Liveness Detection	/identity-documents API SDK: /identity-documents/tokens	Per verification attempt (Billing is based on API success, not whether approve or decline is returned).
AML Transaction Monitoring for fiat	/customers 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 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.

​Invoicing timing and procedures

​Product specific billing

​How usage charges are counted

Invoicing timing and procedures

Product specific billing

How usage charges are counted