FraudRecord fraud checks
connected to BillingServ
Run FraudRecord lookups during checkout and keep the result with the relevant customer and order. FraudRecord receives hashed identity data; BillingServ stores the response for staff review without changing the existing checkout decision.
14-day free trial · No card required · Cancel anytime
What is the FraudRecord integration?
FraudRecord is a customer and order fraud lookup service. BillingServ can query it as part of checkout using normalised, repeatedly hashed identity values such as the customer's email, name and username.
The response can include a status, score, report count, confidence, history score, query ID and result link. BillingServ stores the result against the customer and order so staff can review it later.
Fraud intelligence without changing checkout
FraudRecord checks run synchronously when enabled, but they are currently shadow-only: an APPROVE, REVIEW or ERROR result is recorded for review and does not change the existing checkout decision.
Use the result as another signal during manual review, alongside your existing fraud controls, without sending raw identity data to the provider.
FraudRecord checks connected to customer and order records
Add a privacy-conscious fraud lookup to checkout while BillingServ keeps the result beside the billing activity it relates to.
Hashed identity lookups
BillingServ normalises and hashes customer identity values before sending a FraudRecord query, so raw email and name are not included in the request.
Checkout-time checks
When enabled, BillingServ runs a FraudRecord query during checkout and attaches the result to the current customer and order.
Approve, review or error
Turn FraudRecord responses into APPROVE, REVIEW or ERROR statuses for quick staff triage.
Customer and order history
Results persist on both customer and order records, keeping the fraud context with the billing activity it belongs to.
Reviewable result details
Keep score, report count, confidence, history score, query ID and the provider result link when available.
Shadow-mode by design
FraudRecord findings are stored for review and do not change the existing checkout decision.
Connect FraudRecord once, then review results from BillingServ
Setup is kept in your API integrations and the results stay attached to the billing records they describe.
Add your FraudRecord API key
Enter your 16-character hexadecimal FraudRecord API key in BillingServ and enable the integration.
BillingServ builds a lookup
During checkout, BillingServ normalises customer email, name and username, then hashes each value before sending the query.
FraudRecord returns a result
BillingServ reads the response, including status, score, report count and query ID when those values are available.
Review it in BillingServ
The result is stored on the customer and order for staff review without changing the existing checkout decision.
Add FraudRecord data to the billing record
Fraud checks are more useful when the result is connected to the customer and order context your team already works with.
Because the current integration is shadow-only, it gives staff another signal for review while existing checkout decisions continue unchanged.
Raw identity data stays out of the request
BillingServ sends repeatedly hashed identity values rather than raw customer email, name or username.
Customer and order context
Keep the result beside the customer and order records that prompted the check.
Useful review statuses
See whether a lookup was approved, needs review or could not be completed.
Existing checkout stays unchanged
Use FraudRecord as a review signal while the current checkout decision continues on its existing path.
FraudRecord integration questions
What BillingServ customers need to know before connecting FraudRecord.
What does FraudRecord do in BillingServ?
The integration runs FraudRecord customer and order lookups during checkout when enabled. It stores the returned fraud status and details on the relevant customer and order for staff review.
Does FraudRecord block payments or checkout?
Not currently. FraudRecord runs in shadow mode in BillingServ: its APPROVE, REVIEW or ERROR result is stored for review but does not change the existing checkout decision.
What data does BillingServ send to FraudRecord?
BillingServ normalises customer email, name and username, then sends repeatedly hashed values to FraudRecord. Raw identity values are not included in the API request.
What statuses can FraudRecord return?
BillingServ records APPROVE when no report signal is returned, REVIEW when FraudRecord returns a positive score or report count, and ERROR when the lookup cannot complete or the response is invalid.
Where are FraudRecord results stored?
BillingServ stores the status and JSON result on the customer and, when an order is available, the related order. Returned query IDs link to a FraudRecord result page when available.
Can staff run a FraudRecord check manually?
Yes. Staff with access can run a check from the customer record when the integration is configured and enabled.
What do I need to connect FraudRecord?
You need an active FraudRecord API key and the BillingServ FraudRecord integration enabled. The current key format is a 16-character hexadecimal key.
Bring FraudRecord checks into your billing workflow
Start a BillingServ trial and keep FraudRecord lookup results connected to the customers and orders your team needs to review.
No card required to get started.