Fairfax vs. Production Accounts – Proof Help Center
The Proof Help Center explains that organizations with access to Fairfax, Proof's sandbox environment at https://app.fairfax.proof.com, should use it exclusively for testing and creating mock transactions without real customer data, while the Production environment at https://app.proof.com is for sending actual transactions to customers, emphasizing that Fairfax sends real emails but must never include real customer contact information to avoid privacy issues.
Audience: Organizations
The short answer: Certain organization accounts have access to Fairfax — Proof's sandbox environment where you can test features or experience Proof as a signer without affecting real transactions.
Be sure you're in the intended environment. To test a transaction, use Fairfax. To send a real transaction to an actual signer, use Production.
Fairfax vs. Production Overview
-
Fairfax
- URL: https://app.fairfax.proof.com
- Purpose: Testing Proof, creating mock transactions, understanding the signer experience
- Experience Proof as a signer: Emails sent from Fairfax test accounts are directed to the Fairfax URL above.
-
Production
- URL: https://app.proof.com
- Purpose: Sending actual transactions to your customers
- Experience Proof as a signer: Emails sent from your Production account are directed to the Production URL above.
Fairfax simulates the full transaction experience and actually sends transaction emails. Do not use customer contact information to protect privacy and avoid confusion.
Summary Checklist
- Use Fairfax (https://app.fairfax.proof.com) for testing only.
- Use Production (https://app.proof.com) for real transactions.
- Fairfax sends real emails — never use real customer contact information in the test environment.
Still unsure? Contact Proof Support for help.
Related
Proof’s Technical Rebrand: What Customers Need to Know
Notarize is rebranding to Proof, with all web applications moving from notarize.com to proof.com starting September 14, maintaining existing login credentials and URL redirects, introducing a new recommended API endpoint at api.proof.com alongside the existing one, updating email domains to @proof.com, preserving Single Sign On configurations with new metadata, and running both domains concurrently during a transition period to ensure a smooth customer and partner experience.
Archive or Unarchive Completed Transactions – Proof Help Center
The Proof Help Center explains that completed transactions can be archived individually or in bulk to move them from the All Transactions list to an Archived folder for organization without deletion, and they can be restored anytime by selecting them in the Archived folder and choosing to unarchive either from the transaction list or transaction details.
Delete an OAuth Client Application or Secret – Proof Help Center
The Proof Help Center guide explains that only organization owners or admins can immediately delete an OAuth client application or revoke a client secret—actions that disable authentication for all integrations using those credentials—and recommends rotating secrets instead of deleting active applications, providing step-by-step instructions and warnings about the irreversible impact on connected systems.
Create an OAuth Client Application – Proof Help Center
The Proof Help Center guide explains that organization owners, admins, or users with API management permissions can create OAuth client applications—a paid feature enabled by Proof—to securely connect external systems to Proof accounts using token-based authorization instead of passwords, with each client application having a unique App ID, multiple one-time-viewable App secrets, full API key scope, and tokens that expire every two hours, recommending separate clients for different environments and emphasizing secure storage of secrets.
Edit API-Created EasyLink Settings – Proof Help Center
The Proof Help Center guide explains how organizations can edit API-created EasyLink settings—such as name, payer, signer annotation permissions, ID requirements, transaction details, and signer limits—by logging into their account, navigating to Settings > API Keys, and adjusting options like allow_signer_annotations, require_secondary_photo_ID, external_ID, transaction_type, transaction_name, transaction_doc_category, min_signers, and max_signers, with a maximum of ten devices allowed per meeting including at least one notary and one signer.
eVaults for business – Proof Help Center
Proof integrates with eOriginal to enable business customers to securely eVault PDF documents by setting up their own eOriginal vault, configuring the integration via Proof’s admin panel with eOriginal credentials, marking documents for eVaulting either through the Proof interface or API, and after completing meetings, storing original signed documents in the eOriginal vault while retaining watermarked copies and audit trails within Proof.