An API from Best Pay LLC
Proof your records weren’t changed. Checkable by anyone.
Your software sends the SHA-256 seal of a file. Ninefold writes it to your own write-once ledger, Best Pay signs it with a hardware key, and you get a receipt that anyone can check against our public key, with no account and no call back to us.
- Your files never leave you
- Signed with a hardware key
- Veteran-owned, Texas
# Send the seal, never the file SEAL=$(shasum -a 256 invoice.pdf | cut -c1-64) curl https://api.bestninefold.com/v1/records \ -H "Authorization: Bearer $NINEFOLD_KEY" \ -H "Content-Type: application/json" \ -d '{"ref":"INV-1001","sha256":"'$SEAL'"}'
{
"status": "SEALED",
"seq": 41,
"anchored": false,
"used": 42, "included": 6000
}
Why teams use it
A record you can show to someone who doesn’t trust you.
Logs can be edited. Databases can be rewritten. A Best Pay Receipt is a small signed file: if the record changes by one byte, the check fails.
Invoices and contracts
Prove the invoice or signed contract you hold today is the one you sent on the day you sent it.
Photos and inspections
Seal job-site photos, inspection reports and delivery proof the moment they’re taken.
Logs and audit trails
Give auditors a trail whose earlier lines can’t be quietly changed without the check showing it.
How it works
Five steps, one API call from you.
What a valid receipt shows
- The record (its seal, reference and label) is exactly what was sealed.
- Best Pay’s published key signed the batch it belongs to.
- Anyone can check it, without an account and without asking us.
What it does not claim
- That the file’s contents are true.
- That a payment happened or a person is who they say.
- That a court will accept it.
$49 a month, or $490 a year.
One API key, one private ledger, and a signed receipt for every record.