> ## Documentation Index
> Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Required Setup Steps

> Overview of the required setup steps within the Creditor Portal.

## 1. Merchant Account Connection

### Purpose

Enables the creditor to connect a merchant account for payment processing.
YouNegotiate is payment-processor agnostic and does not process payments directly.

## How It Works

**Option 1: Gateway Connection**
Supported gateways include:

* Authorize.net
* USA ePay
* Stripe (limited relevance)
  User:
* Selects gateway
* Enters credentials
* Selects payment methods:
  * ACH
  * Credit Card
    System:
* Validates credentials
* Establishes connection

***

**Option 2: Tilled Application**
User:

* Submits merchant application
  System:
* Sends application to Tilled
* Receives status:
  * Approved
  * Pending
  * Declined

## Result

* Merchant account connected
* Payment methods enabled
* Required setup step completed
* Settlement and payment plan processing enabled

## Validation Rules

* Valid gateway credentials required
* Supported gateway OR approved Tilled application required
* At least one payment method selected

## Developer Notes

* Support multiple gateway integrations
* Validate credentials securely
* Store tokens/references only
* Tilled workflow is asynchronous
* Status values:
  * not\_started
  * pending
  * completed
* Declined applications must reset setup state cleanly

***

## 2. Create Header Profiles

### Purpose

Maps creditor billing-system data into the YouNegotiate import structure.

### How It Works

User:

* Uploads CSV file
* Maps source fields
* Defines date format
* Saves profile
  System:
* Stores reusable mapping configuration
* Uses profile for manual and SFTP imports

### Result

* Header profile created
* Standardized account imports enabled

### Validation Rules

* At least one profile required
* Required fields must be mapped
* Date format required
* Valid CSV required

### Developer Notes

* Support reusable mappings
* Validate mappings before processing
* Header Profile name must match SFTP folder name
* Birthdate mapping is critical for identity matching

***

## 3. Pay Term Offers

### Purpose

Defines settlement and payment plan offers available to consumers.

### How It Works

System:

* Applies master pay terms
* Applies optional sub-account overrides
* Generates offers during account delivery

### Result

* Offers attached to accounts
* Consumers receive repayment options

### Validation Rules

* Master pay terms required
* Values must be within valid ranges
* Settlement or payment plan configuration required

### Important Business Rule

Delivered offer terms must be stored with the account at the time of offer delivery.
Future changes to master, group, sub-account, or individual offer configurations must not modify previously delivered offers.

### Developer Notes

* Store delivered terms separately from active configuration
* Support master and sub-account overrides
* Store original and discounted balances
* Apply offer hierarchy dynamically

***

## 4. Terms & Conditions Templates

### Purpose

Defines legal agreements used for settlements and payment plans.

### How It Works

User:

* Creates master Terms & Conditions template
* Optionally creates sub-account overrides
  System:
* Applies terms to generated agreements

### Result

* Agreements generated consistently
* Legal language tied to transactions

### Validation Rules

* Master template required

### Developer Notes

* Version all templates
* Support dynamic variables
* Maintain audit trail
* Store terms version with each executed agreement

***

## 5. About Us Profile

### Purpose

Provides company information visible to consumers.

### How It Works

User:

* Creates company profile
* Enters business information
  System:
* Displays profile within the consumer experience

### Result

* Consumers see verified company information
* Improves trust and engagement

### Validation Rules

* Required profile fields must be completed

### Developer Notes

* Tie profile to verified KYB identity
* Cache content appropriately
* Content must be safe for consumer display

***

## Setup Dependency Rules

The following setup steps are required before account import and standard portal workflows are enabled:

* Merchant Account Connected
* At least one Header Profile exists
* Master Pay Terms configured
* Master Terms & Conditions Template created
* About Us Profile completed
  These requirements are hard prerequisites and must be enforced by the system.