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.
Notarize will undergo a number of critical changes as it rebrands to its new company: Proof. Here is what active Notarize customers, partners, and users need to know about upcoming technical changes to prepare for this transition.
- Notarize’s web applications will move to proof.com. URL redirects will keep existing bookmarks and login credentials working.
- The existing API endpoint (api.notarize.com) will be maintained indefinitely. A new endpoint (api.proof.com) will be introduced and recommended for future integrations.
- Email “From” and “Reply-to” addresses will come from @proof.com.
- Notarize’s Single Sign On (SSO) configurations will not have to change. New Proof metadata will be available.
- Notarize.com and proof.com will run side-by-side for a sufficient grace period to help with the transition.
Web Application Changes
Starting September 14, all Notarize web applications at notarize.com will redirect to proof.com. Users can continue using their current login credentials, and redirects will connect Notarize URLs to their new home on Proof.
Production Redirects
- app.notarize.com/* → app.proof.com/*
- business.notarize.com/* → business.proof.com/*
- capture.notarize.com/* → capture.proof.com/*
- notary.notarize.com/* → notary.proof.com/*
- lender.notarize.com/* → lender.proof.com/*
- title.notarize.com/* → title.proof.com/*
- verify.notarize.com/* → verify.proof.com/*
Fairfax Redirects
Fairfax is a standalone, production mirror environment, used by Notarize customers and partners for User Acceptance Testing (UAT) and integration testing.
- app.fairfax.notarize.com/* → app.fairfax.proof.com/*
- business.fairfax.notarize.com/* → business.fairfax.proof.com/*
- capture.fairfax.notarize.com/* → capture.fairfax.proof.com/*
- notary.fairfax.notarize.com/* → notary.fairfax.proof.com/*
- lender.fairfax.notarize.com/* → lender.fairfax.proof.com/*
- title.fairfax.notarize.com/* → title.fairfax.proof.com/*
- verify.fairfax.notarize.com/* → verify.fairfax.proof.com/*
Side-by-Side Configuration
Starting September 14, Notarize will run new proof.com-based web applications side-by-side with its current portals – both in the live production environment and Fairfax test environment – before implementing URL redirects.
API Changes
Notarize will maintain its existing api.notarize.com endpoint indefinitely to support existing integrations. A new endpoint will be introduced at api.proof.com and will be recommended for new integrations.
Both endpoints will allow use of the same API keys. Additional developer documentation about these API changes can be found at dev.notarize.com.
Email Changes
Emails sent by Notarize will update to reflect the Proof rebranding. “From” and “Reply-to” will come from proof.com (e.g., jenny@proof.com and noreply@proof.com).
Notarize uses dedicated IP addresses with its email providers to ensure high rates of email delivery. Notarize will introduce three new dedicated IP addresses for Proof email delivery:
- 149.72.42.13
- 159.183.126.152
- 159.183.92.167
The full list of email sending IPs is available. Additionally, Notarize will be enforcing DMARC on its proof.com based emails.
Additional Recommendations for Readiness
In addition to the above recommendations, Notarize encourages the following steps to support a seamless transition:
- Update corporate firewalls and proxy allow lists to include new *.proof.com URLs.
- Update corporate email spam filters to recognize “From” and “Reply-to” emails from Proof.
- If your organization filters emails based on content, pre-test delivery of new Proof branded emails in the Fairfax environment.
- If your organization filters emails based on the sending IP, update with the new IP addresses listed above.
- Use the side-by-side platforms to pre-test new Proof URLs.
If transition help is needed, contact support@notarize.com.
Related
API Supplement
The API Supplement, effective December 16, 2024, is incorporated into the Proof General Terms and grants Subscribers a limited, revocable license to use Proof’s APIs solely for integrating their applications with Proof’s Services, requires secure handling and non-sharing of API Keys, restricts API use to approved purposes, and governs access to sensitive personal data such as homeowner and financial information under strict compliance conditions.
Set Up a Proof Administrator Account for Adobe Integration
This article guides organizations through setting up a Proof administrator account for Adobe Acrobat Sign integration by accepting an email invitation, creating a password, generating a full access API key in Proof's settings, securely storing the key, and entering it into Adobe Sign's Notary Settings, while emphasizing prerequisites, best security practices, and troubleshooting steps for missing invitations.
Set Up API Users in Encompass – Proof Help Center
The article guides Encompass administrators through creating an API user with specific permissions—including Read/Edit Loans, Edit Subordinate Loans, and Encompass LO Mobile Connect—to enable Proof's integration using provided API keys, and instructs notifying the Proof Solutions Engineer to complete the connection and receive necessary eClosing forms.
Create an Identify Transaction with SoftPro Integration – Proof Help Center
The article provides step-by-step instructions for organizations to create an individual identity verification transaction within SoftPro using Proof integration, requiring a SoftPro transaction, a Proof API key, and navigating through the 360 tab to select and submit the desired identity verification method for one person at a time.
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.
Salesforce: Set Up API for Testing – Proof Help Center
The article explains how Salesforce administrators or owners can enable testing mode in sandbox or developer environments by activating the "Package Testing Mode" in Custom Settings to use the Proof testing API for validating workflows, transaction creation, webhook behavior, and document retrieval during user acceptance testing before switching to the production API, emphasizing best practices and troubleshooting tips for a smooth integration setup.