Creditcrest Sign

Click-to-sign for any document, with evidence you keep.

Sign it. Keep the proof.

Goes in
A document, the signer’s name and the words they agree to
Comes out
Sealed evidence of the signature, and a certificate to keep
Holds the line
Creditcrest keeps nothing: the lender holds the evidence

Try it

Sign an invented agreement

A test request. Nothing you type is kept.

How it works

  1. Your program asks for a signature: the document, the signer’s name and the words they agree to. It gets a link to send.
  2. The signer reads the document, types their name and ticks the box.
  3. You get the evidence back, sealed by Creditcrest, with a certificate of signing. Creditcrest keeps nothing.
  4. Later, anyone holding the evidence can have it checked: unchanged, or exactly why not.

What comes back

The invented agreement, signed as Alex Example. The evidence:

{
  "version": "creditcrest-sign-1",
  "method": "creditcrest-click-to-sign",
  "requestId": "00000000000000000000000000000001",
  "lender": "sandbox",
  "mode": "test",
  "title": "An invented agreement",
  "documentHash": "49bd1ef974a43a455f8028ed432c43276eff0058517ec080c16213b3f1bc65af",
  "documentUrl": null,
  "name": "Alex Example",
  "mark": "alex example",
  "consentText": "I have read the whole document, and I agree to sign it electronically.",
  "consentVersion": "creditcrest-sign-consent-1",
  "contact": null,
  "signedAt": "2026-10-01T00:04:00.000Z",
  "expiresAt": "2026-10-02T00:00:00.000Z",
  "ipHash": "fe8d332dfa465cebcf098c373b33c60966ed0f1f617cfe2e8e3027dcfe96f65c",
  "uaHash": "71dcf3491a461f3c4846e074b8b702ca35c632877e0edb1986be32a1a528c97b"
}

Its seal:

{
  "alg": "HMAC-SHA256",
  "kid": "sandbox",
  "value": "7f18c002c588ce4dd7d7718bbfc62fbffebef5473e83653836c5ff48c0bdfd55"
}

And the certificate of signing that goes with them:

Certificate of signing

Document
An invented agreement
Its fingerprint (SHA-256)
49bd1ef974a43a455f8028ed432c43276eff0058517ec080c16213b3f1bc65af
Signed by
Alex Example
Signature
alex example
Typed as an electronic signature
Signed
1 October 2026 at 10:04 am AEST
2026-10-01T00:04:00.000Z
Agreed to
I have read the whole document, and I agree to sign it electronically. (wording version creditcrest-sign-consent-1)
Asked by
a sandbox key, for testing
Request
00000000000000000000000000000001
Seal
HMAC-SHA256 · key sandbox
7f18c002c588ce4dd7d7718bbfc62fbffebef5473e83653836c5ff48c0bdfd55

Creditcrest can check this evidence and its seal at any time: nothing in it has changed since it was signed if the seal still matches. It does not show who was at the keyboard.

A test signature. It is not a signature on a real document.

Contracts in the borrower’s account

A contract signed in a lender’s hosted borrower account is checked and sealed by the same engine, and is included in the loan’s price.

An outside provider, as a backup

A lender can switch its contracts to an outside e-signature service in its configuration. Creditcrest Sign stays the default, and nothing switches from one to the other unless the lender chooses it.

What it does not prove

Who was at the keyboard: a link works for whoever holds it. A request can ask the signer to confirm an email address or mobile you already hold. Whether click-to-sign meets your legal requirements is for your lawyer.

Price

$0.50 a completed signature through the API. A request nobody signs is free, and so is checking evidence.

For a program

POST /v1/sign/requests asks for a signature and returns the link. POST /v1/sign/evidence opens the evidence the signer brings back. POST /v1/sign/verify checks evidence and its seal. Or check a signature here.