Forth, Inc

Forth Pay

<p class="slate-p " >This section contains any user guides specific to the Forth Credit feature.</p><p class="slate-p " ></p><p class="slate-p " ></p>

User Guides

<p class="slate-p " >The Bulk APIs section makes handling large volumes of data faster and easier. Instead of processing records one by one, you can batch update or upload multiple entries in a single request—saving time and improving efficiency. Whether you&apos;re managing massive datasets or streamlining workflows, this functionality is built to optimize performance and keep operations running smoothly.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Bulk APIs

<p class="slate-p " >The Compliance section is here to help you stay on top of regulatory requirements with ease. Instead of navigating complex compliance rules on your own, this section gives you the tools and guidance to keep your projects aligned with industry standards. Whether it’s data security, financial regulations, or governance, it’s designed to make compliance feel less overwhelming, so you can focus on building with confidence.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Compliance

<p class="slate-p " >The Core Objects section is the backbone of customer management, handling everything from interactions and accounts to financial agreements. Whether you&apos;re managing contacts, companies, debts, documents, enrollments, loans, or settlement offers, this section keeps everything organized and accessible. It ensures smooth communication and tracking, helping you maintain clarity and efficiency in client-related activities.</p><div class="slate-hr"><hr contenteditable="false" class="slate-HrElement-hr"/></div><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Core Objects

<p class="slate-p " >The Lookups section is designed to make searching and managing predefined data effortless. Instead of manually keeping track of things like templates, hold reasons, types, subtypes, and statuses, this tool provides a structured way to retrieve and organize key reference information. Whether you need to pull status updates or filter through categories, everything is accessible exactly when you need it, keeping operations smooth and efficient.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Lookups

<p class="slate-p " >The Processing section keeps draft management and fee handling organized and hassle-free. Users can create, update, retrieve, or delete drafts, with the flexibility to activate, deactivate, or cancel them as needed. It also provides easy access to ACH credit fee information, enabling users to view and modify fees without having to dig through complicated records. Everything is designed to keep workflows efficient and structured.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Processing

<p class="slate-p " >The Reporting section offers users powerful insights into their transactions, clients, holds, debts, and settlements. With access to detailed reports and analytics, users can track performance, analyze trends, and make informed decisions to optimize their business operations. This functionality provides a clear and structured view of financial data, ensuring efficient management and strategic planning.</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

Reporting

Clixsign

<p class="slate-p " >This section contains a user guide specific to the Clixsign feature. Clixsign is Forth&apos;s proprietary electronic document signing platform. To enable this platform, please contact <a href="mailto:Support@setforth.com" target="_self">Support@setforth.com</a>.</p><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p " >This endpoint allows you to initiate the sending of a Clixsign document to a specified client. By providing the necessary documents and signer details, you can trigger the document delivery process efficiently.</p><p class="slate-p " ></p><p class="slate-p " ></p>

Create Signing Request

Blank

Forth Pay API

Api-Key

Production

Sandbox

Activate Debit

Activate Fee

Activate Refund

Activate Settlement Payment

Add Bank Account

Add Comment

All Settlement Decisions by Date

Attach Settlement Letter

Bank Accounts

Cancel Enrollment

Cancel Unprocessed Debit

Cancel Unprocessed Fee

Cancel Unprocessed Refund

Cancel Unprocessed Settlement Payment

Client Balance Reports

Client Report

Clients on Gateway Hold

Request a Signature

Companies

Clients

Create ACH Credit Fee

Create Co-Applicant

Create Company

Create Client

Create Debit

Create Debt

Create Forth Pay Creditor

Create Forth Pay Portal User Account

Create ForthPay Creditor Address

Create Multiple Drafts / Debits

Create Performance Fee

Create Refund

Create Settlement

Create Settlement Payment

Creditors

Deactivate Debit

Deactivate Fee

Deactivate Refund

Deactivate Settlement Payment

Debits

Debts

Decisions

Delete Unprocessed Debit

Documents

Enroll Client

Enrolled Clients

Enrollment

Fees

Forth Pay API Workflow Guide

Forth Pay Quick Start Guide

Generate Account Closure Form

Generate Bank Change Document

Generate CAA Document

Generate Document Based on Lookup Key

Generate One Time Debit Document

Generate Risk Returns Form

Request Hold Release

Get Bank Account

Get All Companies

Payees

Get Payee

Update Payee

Get All Documents

Get Document

Upload Document

Graduate Enrollment

Pause Enrollment

Re-Enroll Client

Resume Enrollment

Get Client

Portal

Send Password Reset Email

Update Co-Applicant

Update Client

Get All Creditors

Get Creditor

Get Debt

Update Debt

Settlement Offers

Get Settlement

Update Settlement

Void Settlement

Virtual Bank Accounts (VBA)

Get All VBAs

Get VBA

Get VBA Activity

Update VBA Reserve Amount

VBA to Client Funds Transfer

VBA to VBA Funds Transfer

Get Cancellation Reasons

Get Compensation Templates

Get Decision Statuses

Get Document Templates

Get Document Types

Get Forth Fee Amounts

Get Freeze Map

Get Hold Reasons

Get Settlement Offer Statuses

Get Transaction Statuses

Get Transaction Subtypes

Get Transaction Types

Get Check Image

Get Settlement Decision

Mark  as Paid

Mark as Returned

Transactions

Get Debit

Update Debit

Get Fee

Update Fee

Refunds

Get Refund

Update Refund

Settlement Payments

Get Settlement Payment

Update Settlement Payment

Outstanding Debts

Settlements

Shipped Check Payments

<div class="slate-div"><p class="slate-p " ></p><h1 class="slate-h1 " >Introduction</h1><p class="slate-p " >This guide has been developed to describe elements of the FORTH Pay API system, with detailed descriptions of each endpoint to inform you how our API framework works. </p><ul class="slate-ul " ><li class="slate-li " ><div style="position:relative">For information on Authentication and Authorization, Click <a href="https://developer.setforth.com/api/get-started-2/authentication-1" target="_blank">HERE</a></div></li><li class="slate-li " ><div style="position:relative">For information on our Commonly Used Error Codes, Click <a href="https://developer.setforth.com/api/get-started-2/error-codes" target="_blank">HERE</a></div></li><li class="slate-li " ><div style="position:relative">For important notes and reminders, go the end of this article.</div></li></ul><p class="slate-p " ></p><div style="text-align:left"><img src="https://d24lr4zqs1tgqh.cloudfront.net/0fc15548-267e-4b66-b09a-e7ba69d93afb.png" style="
              width:1114px;
	            height:508px;
	            aspect-ratio:1114 / 508"
         /></div><p class="slate-p " ></p><p class="slate-p " ></p><h1 class="slate-h1 " >General Workflow</h1><p class="slate-p " >Use the endpoints listed below in the order they are listed to facilitate your API experience with FORTH Pay.</p><p class="slate-p " ></p><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >1</h6><h3 class="slate-h3 " >Create Consumer</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/consumers/create-consumer" target="_blank">This endpoint</a> makes it efficient to add a new client, just enter their details, like the name, contact info, and any initial settings, and the system will set up the record for you. No manual data entry, just a quick and efficient way to keep client information organized.</p><p class="slate-p " > </p></div></div></div><p class="slate-p " ></p><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >2</h6><h3 class="slate-h3 " >Add Bank Account</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api-runner/setforth/api/forth-pay-3/core-objects-2/bank-accounts/add-bank-account" target="">This endpoint </a>sets up a bank account to fund the Forth Pay custodial account, keeping things efficient. Only one account can be on file, and adding a new one replaces the existing one. Users can provide details like account number, routing number, account type, and client/customer ID in the request body. If the client is currently enrolled, a hold will be placed, and a new bank authorization form will be needed to lift it.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >3</h6><h3 class="slate-h3 " >Create Debt</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/debts-1/create-debt-1" target="">This<strong class="slate-bold"> </strong>endpoint</a> creates a debt record for a client, capturing essential details like creditor, debtor (client_id), debt amount, and due date. It is designed to keep debt tracking clear and organized, ensuring everything is properly documented for easy management. </p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >4</h6><h3 class="slate-h3 " >Upload a Document <em class="slate-italic">(Optional)</em></h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-crm-3/core-objects-1/document-package" target="_blank">This endpoint</a> uploads a Forth Pay document and links it to a specific client, identified by {id}. The document is included in the request body as multipart/form-data, ensuring a secure and efficient association with the client’s record
</p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >5</h6><h3 class="slate-h3 " >Enroll Consumer</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/consumers/enrollment/enroll-consumer" target="">This endpoint</a> allows users to enroll a specific client into a Forth program or service, providing enrollment details like program options and start dates in the request body. This section facilitates the seamless onboarding of clients into the desired program, streamlining the enrollment process for administrators and ensuring a smooth experience for clients.</p></div></div></div><p class="slate-p " ></p><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >6</h6><h3 class="slate-h3 " >Create Multiple Drafts/Debits</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/bulk-apis-2/create-multiple-drafts-debits" target="">This endpoint</a> lets you create several draft items at once, saving you time and effort. Instead of adding them one by one, you can send a single request with a JSON array of drafts, making bulk processing smooth and efficient. If you’re managing multiple transactions, this is the perfect way to keep things streamlined.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >7</h6><h3 class="slate-h3 " >Create Settlement</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-crm-3/servicing-1/settlement-offers-1/create-settlement-offer-1" target="">This endpoint</a> creates a new client settlement entry, requiring an array of settlement payment objects for proper setup. Before proceeding, use creditor endpoints to query for valid creditors. The request body should contain a JSON object outlining the settlement details, ensuring all relevant data is included.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >8</h6><h3 class="slate-h3 " >Create Settlement Payment</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/settlement-payments/create-settlement-payment" target="">This endpoint</a> creates a new payment record within a settlement entry, allowing users to initiate a payment with all necessary details. The request body should include a JSON object specifying the payment information, ensuring everything is clear and properly structured. </p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >9</h6><h3 class="slate-h3 " >Get All Creditors</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/creditors/get-all-creditors" target="">This endpoint</a> provides you a comprehensive view of all creditors associated with a project, enabling easy organization and access to key creditor details. You can filter and sort creditors based on specific criteria, such as name or location, streamlining financial coordination and management within the project.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >10</h6><h3 class="slate-h3 " >Update Consumer</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/consumers/update-consumer" target="">If you need to update a client’s details</a>, enter their unique {id} and specify the fields that need to be changed. Instead of hunting down records manually, you can streamline updates and keep client information accurate and up to date
</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >11</h6><h3 class="slate-h3 " >Update Fee</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/fees/update-fee" target="">This endpoint </a>lets you update an existing fee configuration, identified by its unique {id}. The request body should include a JSON object with the new details, ensuring the fee remains accurate and properly structured.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >12</h6><h3 class="slate-h3 " >Create ACH Credit Fee</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/fees/create-ach-credit-fee" target="">This endpoint</a> creates a new ACH credit fee entry, making it easy to define and configure fees for Automated Clearing House (ACH) credit transactions. The request body should include all necessary details to ensure accurate fee processing.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >13</h6><h3 class="slate-h3 " >Create Performance Fee</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/fees/create-performance-fee" target="">This endpoint</a> sets up a new performance fee entry, allowing users to define fees based on performance metrics. The request body should include all necessary details to ensure accurate configuration and application of the fee.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >14</h6><h3 class="slate-h3 " >Get Settlement Payment</h3><p class="slate-p " ><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/settlement-payments/get-settlement-payment" target="">This endpoint</a><strong class="slate-bold"> </strong>lets users access specific payment details using a unique identifier, making financial tracking simple and efficient. Users can view transaction type, amount, and key dates, ensuring clear and accurate record-keeping. With this functionality, managing client payments is straightforward and hassle-free.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >15</h6><h3 class="slate-h3 " >Activate Settlement Payment</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/settlement-payments/activate-settlement-payment" target="">This endpoint</a> activates a specific payment record, identified by its unique {id}, setting the payment into motion. Once active, the payment moves forward in processing or finalization within the system.</p><div class="slate-code_line">
</div></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >16</h6><h3 class="slate-h3 " >Activate Fee</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/processing-1/transactions/fees/activate-fee" target="">This endpoint </a>activates a specific fee entry, identified by its unique {id}, making it applicable for transactions and processes. Once activated, the fee can be used as intended within the system.</p><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >17</h6><h3 class="slate-h3 " >Graduate Enrollment</h3><p class="slate-p " ><strong class="slate-bold"> </strong><a href="https://developer.setforth.com/api/forth-pay-3/core-objects-2/consumers/enrollment/graduate-enrollment" target="">This endpoint</a> confirms a client’s successful completion or graduation from an enrolled program, using their unique {id} for identification. This action may update their status or modify associated records, ensuring their progress is accurately reflected in the system.</p><p class="slate-p " ></p><h4 class="slate-h4 " ><em class="slate-italic"><strong class="slate-bold">NOTE </strong></em><strong class="slate-bold">:</strong> Cancellation of a program is possible. Use the <a href="https://developer.setforth.com/api-runner/setforth/api/forth-pay-3/core-objects-2/consumers/enrollment/cancel-enrollment" target="_blank">Cancel Enrollment</a> endpoint to remove a client from an enrolled program or service, using their unique {id} for identification. The reason_id parameter allows users to specify the reason for cancellation. You may also use the <a href="https://developer.setforth.com/api-runner/setforth/api/forth-pay-3/compliance/documents-1/generate-account-closure-form" target="_blank">Generate Account Closure Form</a> endpoint.</h4><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >18</h6><h3 class="slate-h3 " >Request Hold Release</h3><p class="slate-p " >If a client has a hold that needs to be lifted, <a href="https://developer.setforth.com/api/forth-pay-3/compliance/documents-1/request-hold-release" target="">this endpoint</a> lets you request its removal from a program or obligation. Since some holds might need approval or have specific conditions, the system ensures everything is handled properly before finalizing the release. It’s a straightforward way to keep things moving while following the necessary steps.</p></div></div></div><p class="slate-p " ></p><p class="slate-p " ></p><h1 class="slate-h1 " >Additional Information</h1><p class="slate-p " ></p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative">Not Sufficient Funds (NSF) indicates a returned transaction, when your client has insufficient funds. This directly impacts Forth Pay return rates, and our objective is to keep return rates low. Once a client has an NSF, their account is placed on hold. If the clients wishes to continue with the program, they will have to sign the Forth Pay Auth Doc Risk Return Form.</div></li><li class="slate-li " ><div style="position:relative">For some drsps, a client&apos;s account could be put on hold after one NSF. For others, it may take two or more NSFs for the same action to occur. This is because the business rules for placing a client&apos;s account on hold differ for each drsp.</div></li></ol></div><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p " >This guide provides the steps you should follow to request a signature via Clixsign using the Forth API. To generate a document and send it to Clixsign, you must first have the following information available:</p><ol class="slate-ol " ><li class="slate-li " ><div style="position:relative"> The document template ID you wish to generate and send through Clixsign</div></li><li class="slate-li " ><div style="position:relative"> The contact ID you wish to originate the Clixsign request for</div></li><li class="slate-li " ><div style="position:relative"> The details of the various individuals or entities that are signers on the agreement</div></li></ol><p class="slate-p " >To successfully send a Clixsign document, complete the following steps.</p><p class="slate-p " ></p><div class="steps-widget" style="width:100%;
  	min-width:100%;"><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >1</h6><h3 class="slate-h3 " >Determine Document Template / Package To Be Sent For Signature</h3><p class="slate-p " >Your FORTH CRM account will contain various documents and document packages stored within the ‘Docs’ tab of your system. Navigate to this tab to see what documents you have available for generation, or retrieve them programatically via a GET request to the <a href="68363322f4389be3769c854e/68363346f54809cab573a4f1/68363473bd2e5d23a8e57fdd/68362d44f4389be3769c343e" target=""><code class="slate-code">list-all-documents</code> </a>endpoint. You can retrieve all packages similarly through the documents tab UI or via the endpoint <a href="68363322f4389be3769c854e/68363346f54809cab573a4f1/68363477bd2e5d23a8e57fea/68362d44f4389be3769c34c2" target=""><code class="slate-code">list-document-packages</code></a>. You will need the corresponding ‘Template ID’ or ‘Package ID’ in the following step.</p><div style="text-align:left"><img src="https://d24lr4zqs1tgqh.cloudfront.net/08188dc4-f588-48d5-baba-f62bd758f1f3.jpg" style="
              width:971px;
	            height:475px;
	            aspect-ratio:971 / 475"
         /></div><p class="slate-p " ></p></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >2</h6><h3 class="slate-h3 " >Generate Document Template/Package to Prepare For Signature</h3><p class="slate-p " >Next, use the <a href="68362d44f4389be3769c46c7/68362d44f4389be3769c3482/68362d44f4389be3769c314b" target=""><code class="slate-code">generate-a-document</code></a> endpoint or the <a href="68362d44f4389be3769c46c7/68365061f4389be3769d0955/68362d44f4389be3769c3304" target=""><code class="slate-code">generate-a-document-package</code> </a>endpoint, and reference the corresponding document template ID or package ID you wish to generate for a contact record. In the response, you will receive a <code class="slate-code">doc_id</code> that needs to be referenced in the following request.</p><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{
    &quot;response&quot;: {
        &quot;html&quot;: null,
        &quot;doc_id&quot;: 37256536,
        &quot;doc_data&quot;: {
            &quot;signers&quot;: {
                &quot;1&quot;: {
                    &quot;signer_type&quot;: &quot;Signature here&quot;,
                    &quot;default&quot;: &quot;contact&quot;,
                    &quot;signatures&quot;: [
                        {
                            &quot;type&quot;: &quot;SIGNATURE&quot;,
                            &quot;x&quot;: &quot;78.138&quot;,
                            &quot;y&quot;: &quot;288.008&quot;,
                            &quot;width&quot;: &quot;110.959&quot;,
                            &quot;height&quot;: &quot;27.740&quot;,
                            &quot;required&quot;: true,
                            &quot;page&quot;: 0
                        },
                        {
                            &quot;type&quot;: &quot;INITIAL&quot;,
                            &quot;x&quot;: &quot;452.664&quot;,
                            &quot;y&quot;: &quot;325.468&quot;,
                            &quot;width&quot;: &quot;37.500&quot;,
                            &quot;height&quot;: &quot;18.750&quot;,
                            &quot;required&quot;: true,
                            &quot;page&quot;: 0
                        },
                        {
                            &quot;type&quot;: &quot;TEXTINPUT&quot;,
                            &quot;x&quot;: &quot;215.328&quot;,
                            &quot;y&quot;: &quot;335.734&quot;,
                            &quot;width&quot;: &quot;79.109&quot;,
                            &quot;height&quot;: &quot;10.788&quot;,
                            &quot;required&quot;: true,
                            &quot;page&quot;: 0,
                            &quot;replaceable&quot;: {
                                &quot;text&quot;: &quot;Text&quot;,
                                &quot;font&quot;: &quot;droid_sans&quot;,
                                &quot;size&quot;: 10,
                                &quot;color&quot;: &quot;#000&quot;,
                                &quot;alignment&quot;: &quot;left&quot;,
                                &quot;bold&quot;: false,
                                &quot;italic&quot;: false,
                                &quot;wrap&quot;: true,
                                &quot;fill&quot;: false
                            }
                        }
                    ]
                },
                &quot;2&quot;: {
                    &quot;signer_type&quot;: &quot;&quot;,
                    &quot;default&quot;: &quot;manual&quot;,
                    &quot;signatures&quot;: [
                        {
                            &quot;type&quot;: &quot;SIGNATURE&quot;,
                            &quot;x&quot;: &quot;226.709&quot;,
                            &quot;y&quot;: &quot;293.602&quot;,
                            &quot;width&quot;: &quot;52.397&quot;,
                            &quot;height&quot;: &quot;13.099&quot;,
                            &quot;required&quot;: true,
                            &quot;page&quot;: 0
                        }
                    ]
                },
                &quot;3&quot;: {
                    &quot;signer_type&quot;: &quot;&quot;,
                    &quot;default&quot;: &quot;manual&quot;,
                    &quot;signatures&quot;: [
                        {
                            &quot;type&quot;: &quot;SIGNATURE&quot;,
                            &quot;x&quot;: &quot;314.640&quot;,
                            &quot;y&quot;: &quot;290.496&quot;,
                            &quot;width&quot;: &quot;52.397&quot;,
                            &quot;height&quot;: &quot;13.099&quot;,
                            &quot;required&quot;: false,
                            &quot;page&quot;: 0
                        }
                    ]
                },
                &quot;4&quot;: {
                    &quot;signer_type&quot;: &quot;&quot;,
                    &quot;default&quot;: &quot;manual&quot;,
                    &quot;signatures&quot;: [
                        {
                            &quot;type&quot;: &quot;SIGNATURE&quot;,
                            &quot;x&quot;: &quot;405.155&quot;,
                            &quot;y&quot;: &quot;285.841&quot;,
                            &quot;width&quot;: &quot;52.397&quot;,
                            &quot;height&quot;: &quot;13.099&quot;,
                            &quot;required&quot;: false,
                            &quot;page&quot;: 0
                        }
                    ]
                }
            },
            &quot;pages&quot;: [
                {
                    &quot;width&quot;: 612,
                    &quot;height&quot;: 792
                },
                {
                    &quot;width&quot;: 612,
                    &quot;height&quot;: 792
                }
            ],
            &quot;filename&quot;: &quot;&quot;
        },
        &quot;title&quot;: &quot;Clixsign template 4 signer&quot;
    },
    &quot;status&quot;: {
        &quot;code&quot;: 200
    }
}</div></code></pre></div><p class="slate-p " >Additionally, you should see a corresponding history event and document generated on the contact record in the CRM.</p><div style="text-align:left"><img src="https://d24lr4zqs1tgqh.cloudfront.net/caa3e7df-9edd-4443-8612-e92c3da00eae.jpg" style="
              width:664px;
	            height:108px;
	            aspect-ratio:664 / 108"
         /></div><div style="text-align:left"><img src="https://d24lr4zqs1tgqh.cloudfront.net/2296e6ff-26a2-4a98-80e1-fb43f9173b4a.jpg" style="
              width:780px;
	            height:220px;
	            aspect-ratio:780 / 220"
         /></div></div></div><div class="steps-wrapper"><div class="steps-content"><h6 class="slate-h6 " >3</h6><h3 class="slate-h3 " >Send via Clixsign for Signature</h3><p class="slate-p " >The <code class="slate-code">doc_id</code> value from the previous request will now be used to send a document through Clixsign via the <a href="68362d44f4389be3769c46c7/68362d43f4389be3769c2c12/683649d4f54809cab57414ec/68362d43f4389be3769c2af0" target=""><code class="slate-code">send-clixsign-document</code></a> request with the ‘gen_id’ field in the request body.</p><p class="slate-p " >Additionally, define the values of the signer as if you were generating the document for the contact record within the FORTH UI, including details such as the signer&apos;s name, email, and phone numbers, and whether they are receiving this document via email or SMS message.</p><div style="width:100%;
	min-width:100%;" class="callout-widget" data-type=info ><div class="callout-icon"><svg width="20" height="20" viewBox="0 0 20 20" fill="none" xmlns="http://www.w3.org/2000/svg"><path d="M10.0628 14.1676C10.2434 14.1676 10.3927 14.1086 10.5107 13.9905C10.6288 13.8725 10.6878 13.7232 10.6878 13.5426V9.77177C10.6878 9.6051 10.6253 9.46274 10.5003 9.34469C10.3753 9.22663 10.2295 9.1676 10.0628 9.1676C9.88227 9.1676 9.73296 9.22663 9.61491 9.34469C9.49685 9.46274 9.43783 9.61205 9.43783 9.7926V13.5634C9.43783 13.7301 9.50033 13.8725 9.62533 13.9905C9.75033 14.1086 9.89616 14.1676 10.0628 14.1676ZM10.0003 7.62594C10.1948 7.62594 10.358 7.56344 10.4899 7.43844C10.6219 7.31344 10.6878 7.15371 10.6878 6.95927C10.6878 6.76482 10.6219 6.59816 10.4899 6.45927C10.358 6.32038 10.1948 6.25094 10.0003 6.25094C9.80588 6.25094 9.64269 6.32038 9.51074 6.45927C9.3788 6.59816 9.31283 6.76482 9.31283 6.95927C9.31283 7.15371 9.3788 7.31344 9.51074 7.43844C9.64269 7.56344 9.80588 7.62594 10.0003 7.62594ZM10.0003 18.3343C8.81977 18.3343 7.72255 18.1225 6.70866 17.6989C5.69477 17.2752 4.81283 16.6884 4.06283 15.9384C3.31283 15.1884 2.72602 14.3065 2.30241 13.2926C1.8788 12.2787 1.66699 11.1815 1.66699 10.0009C1.66699 8.83427 1.8788 7.74399 2.30241 6.7301C2.72602 5.71621 3.31283 4.83427 4.06283 4.08427C4.81283 3.33427 5.69477 2.74399 6.70866 2.31344C7.72255 1.88288 8.81977 1.6676 10.0003 1.6676C11.167 1.6676 12.2573 1.88288 13.2712 2.31344C14.285 2.74399 15.167 3.33427 15.917 4.08427C16.667 4.83427 17.2573 5.71621 17.6878 6.7301C18.1184 7.74399 18.3337 8.83427 18.3337 10.0009C18.3337 11.1815 18.1184 12.2787 17.6878 13.2926C17.2573 14.3065 16.667 15.1884 15.917 15.9384C15.167 16.6884 14.285 17.2752 13.2712 17.6989C12.2573 18.1225 11.167 18.3343 10.0003 18.3343ZM10.0003 17.0843C11.9448 17.0843 13.6114 16.3898 15.0003 15.0009C16.3892 13.612 17.0837 11.9454 17.0837 10.0009C17.0837 8.05649 16.3892 6.38982 15.0003 5.00094C13.6114 3.61205 11.9448 2.9176 10.0003 2.9176C8.05588 2.9176 6.38921 3.61205 5.00033 5.00094C3.61144 6.38982 2.91699 8.05649 2.91699 10.0009C2.91699 11.9454 3.61144 13.612 5.00033 15.0009C6.38921 16.3898 8.05588 17.0843 10.0003 17.0843Z" fill="#3960B4"></path></svg></div><div ><p class="slate-p " >NOTE: If ‘enforce_order’ is set to ‘true’, then each signer must complete the document before sending to the next signer in numerical order defined by the request.</p></div></div><div class="slate-code_line"></div><div class="code-block-wrapper"  style="width:100%;min-width:100%" ><div class="code-block-header">JSON</div><pre class="slate-CodeBlockElement slate-code_block"><textarea id="publishedPageCodeblock" style="display:none !important; visibility: hidden; opacity: 0; width: 1px; height: 1px;" type="hidden"> </textarea><code class="language-json keep-markup drop-tokens"><div class="slate-code_line">{
  &quot;gen_id&quot;: 37256536,
  &quot;request_settings&quot;: {
    &quot;enforce_order&quot;: true,
    &quot;expiration_date&quot;: &quot;2025-07-18&quot;
  },
  &quot;notifications&quot;: {
    &quot;email&quot;: {
      &quot;message&quot;: &quot;Thisis your document to sign&quot;
    }
  },
  &quot;signers&quot;: [
    {
      &quot;signer_number&quot;: 1,
      &quot;signer_type&quot;: &quot;Contact&quot;,
      &quot;signer_name&quot;: &quot;Bob Test&quot;,
      &quot;signer_email&quot;: &quot;test@test.net&quot;,
      &quot;signer_phone&quot;: 16665554444,
      &quot;verbal_auth&quot;: true,
      &quot;signer_notifications&quot;: {
        &quot;email&quot;: true,
        &quot;sms&quot;: false
      }
    }
  ]
}</div></code></pre></div><p class="slate-p " >Once all signers are defined and the request is sent, the Clixsign documents will be sent to their respective recipients via their specified delivery methods.</p><p class="slate-p " >Once all documents have been signed, you should see the document status updated to ‘Completed’ within the contact record in the FORTH CRM. </p></div></div></div><p class="slate-p " ></p><p class="slate-p " ></p>

<p class="slate-p " >This section contains any user guides specific to the Forth Pay</p><p class="slate-p " ></p><p class="slate-p " ></p><p class="slate-p " ></p>

This section contains any user guides specific to the Forth Pay

Sections

User Guides

What made this section unhelpful for you?

On this page