Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Digital Core
Modernize with cloud-native core banking technology.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.
More info

Onboarding to use TP_DocuSign_GCP

Tutorials > DocuSign > Onboarding to use TP_DocuSign_GCP

Onboarding a Customer

To onboard a new customer/financial institution, complete these steps:

  1. Create the service account user for the customer within DocuSign. The customer completes this step.
  2. Fetch customer user information from DocuSign needed for the integration. The customer completes this step, and then sends the information to Jack Henry.
  3. Log in to the service account in DocuSign, and then complete the OAuth User Authorization flow. The customer completes this step.
  4. Update translation configuration to add information from Step #2. Jack Henry completes this step.

Step 1: Creating a User for the integration

Each Customer/Financial Institution needing to use JHA’s DocuSign provider must have an account with DocuSign.

New Users can be added via the DocuSign Admin Dashboard at:

After the account is created, additional users can be added. It is recommended that there be a generic service account with an email address attached to the account. Use this generic service account to grant access to the translation layer to act on behalf of the DocuSign account.

Step 2: Obtain Customer User information

There are 3 pieces of data needed from this site for configuration that can be found on the Settings page under Integrations:Apps and Keys.

Reference Image

API Account Id

This is available near the top of the Admin->INTEGRATIONS->Apps and Keys page in DocuSign

Reference Image

BaseUri

This is available near the top of the Admin->INTEGRATIONS->Apps and Keys page in DocuSign

Reference Image

DocuSignUserId

Please Note
NOTE: Make sure that the User ID provided is the one for the newly created service account discussed in Step 1 and not the User ID of the customer’s DocuSign admin.

This is the value from the box labeled “My Account Information”

Reference Image

After obtaining this information, provide it to your Jack Henry contact. These pieces of data are not considered sensitive information.

Step 3: OAuth User Authorization

After the account outlined in Step 1 is created, the customer must grant Jack Henry’s translation service access to the translation layer.

This step is accomplished by logging in as the new service account user. Then, visit one of the following URLs (depending on which JH environment a customer is integrating with):

It also possible to visit the links directly, and then log in to DocuSign.

When granting access, the newly created generic service account must be used.

Have a Question?
Did this page help you?
Last updated Mon Aug 4 2025