Audit trail

When a sale is questioned, the audit trail answers.

Third-party verification is only worth what you can prove. VerifiMe records every event in a verification's life, from creation to signature, with the technical evidence behind it, in a separate internal report your customer never sees.

Audit trail · VF-26-104823 · internal only
Verification createdvia API · key ••••3f9a · ref DEAL-20931
SMS sentto +1 ··· ··· ··72 · dedicated number
SMS deliveredcarrier confirmation received
Link openedIP 99.231.··.·· · iOS 18 · Safari
Passcode confirmed1st attempt · code sent 15:38:21
Answers submitted6 of 6 · 0 failed
Signature captureddrawn on device
Report issuedPDF emailed to customer · record sealed

Sample audit trail · illustrative data · EDT

In detail

What's included.

Every event, timestamped

VerifiMe logs the full chain of custody: when the verification was created and by whom, when each message was sent and delivered, when the customer opened the link, when each answer was submitted, when the passcode was confirmed, when they signed, and when the report was issued.

  • Creation, send, delivery, open and completion events
  • Each answer recorded with its own timestamp
  • Resends, expiry and failures logged too
  • Times recorded to the second, in a consistent time zone

Technical evidence behind each action

Alongside each event, VerifiMe captures the details that show who took the action and from where. This is the evidence regulators, chargeback teams and courts ask for when a customer says "I never agreed to that."

  • IP address of the device that completed the verification
  • Browser and device information
  • Phone number and email the verification was delivered to
  • One-time-passcode confirmation, when identity checks are enabled

Kept apart from the customer's copy

The audit trail is a separate report, available only to your organization. It is never shown on the verification page and never attached to the customer's email. Your evidence stays yours, and your customer gets a clean, readable confirmation.

  • Internal-only report, per verification
  • Never sent or visible to the customer
  • Available to authorized users in your portal
  • Exportable when you need to respond to a complaint

Two records, two audiences

What's in the audit trail, and what the customer sees.

The customer report is for the customer. The audit trail is for you, your compliance team, your lender or a regulator. They're produced together and never merged.

EventEvidence recordedAudit trailCustomer report
Verification createdWho or what created it (user or API key), reference, questionnaire versionYesNo
Message sent / deliveredChannel, destination, sender, delivery statusYesNo
Link openedTime, IP address, device and browserYesNo
PasscodeSent, entered, success or failure, attemptsYesNo
Each answerQuestion as displayed, answer given, timestamp, pass/failYesAnswers only
SignatureCaptured image and timeYesSignature image
Fail rule triggeredRule, message shown, alert recipientsYesMessage only
Resend / expiryWho resent, when, expiry date reachedYesNo
Report issuedPDF generated, emailed to customerYesReceives PDF

When you'll use it

The moments the audit trail earns its keep.

Customer complaints

A customer says they never agreed. You show when they opened the link, the device they used, the answers they gave and the signature they drew.

Lender and chargeback reviews

Finance partners and payment processors ask for proof of authorization. Export the audit trail alongside the signed report.

Regulatory inquiries

When a regulator asks how a contract was verified, show a consistent, timestamped process applied to every customer.

Rep-completed verifications

Device and IP data, plus optional passcodes, help reveal when someone other than the customer completed a verification.

Internal quality reviews

Compare fail rates and completion patterns by rep, store or dealer to find coaching opportunities.

Commission disputes

Operations, sales and accounting agree on what was sold and when, because they're looking at the same confirmed record.

Events loggedCreated, sent, delivered, opened, answered, passcode, signed, completed, failed, resent, expired
Evidence capturedIP address, device and browser, delivery address, timestamps
VisibilityYour organization only; never shared with the customer
FormatSeparate report per verification, exportable
IntegrityCompleted records are not edited after the fact

FAQ

Questions we hear often

Why is the audit trail separate from the customer report?
Because they serve different readers. The customer needs a clear record of what they agreed to. You need technical evidence. Keeping them apart means your customer doesn't receive IP logs, and your evidence isn't diluted into a consumer-facing document.
Can a completed verification be edited?
No. Once a customer completes a verification, the answers, signature and events are fixed. If something needs to change, you send a new verification, and both are kept.
Who can view audit trails?
Authorized users in your organization through the VerifiMe portal. Customers cannot access them.

See VerifiMe on your own sales process.

We'll build a sample questionnaire from one of your real contracts and walk your team through the customer experience, the report and the audit trail.