CSV import enables you to add multiple merchants to Preczn in a single batch—more efficient than creating merchants individually through the Dashboard or API. This process is managed with assistance from Preczn support.

📘
Support-Assisted Process
CSV imports are processed by Preczn support. You'll work with your account manager or [email protected] to obtain templates, submit files, and receive results.

Import Process

Step 1: Request the Template

Contact your Preczn account manager or email [email protected] to request the current CSV import template.

The template includes columns for:

Merchant business information
Owner details
Bank account information
Connection credentials (columns vary based on your configured connections)
Plan assignments
Merchant enablement status

🚧
Template Updates
Request a new template whenever you add connections to your platform. New connections add credential columns that won't exist in older templates.

Step 2: Prepare Your Data

Required Identifier

Each row must include a platformUID—your unique identifier for the merchant. This value appears in the results file, allowing you to match imported merchants to their new Preczn merchant IDs (mid_).

You can optionally include an externalId for additional reference.

Multiple Owners

The template uses numbered columns for owner data:

First Owner	Second Owner
`owner.0.firstName`	`owner.1.firstName`
`owner.0.lastName`	`owner.1.lastName`
`owner.0.ownershipPercentage`	`owner.1.ownershipPercentage`

Add columns following this pattern for additional owners (e.g., owner.2.firstName for a third owner).

Multiple Bank Accounts

Bank accounts follow the same numbered pattern:

Primary Account	Secondary Account
`bankAccount.0.routingNumber`	`bankAccount.1.routingNumber`
`bankAccount.0.accountNumber`	`bankAccount.1.accountNumber`

Data Validation

The import applies the same validation rules as the Merchant API. Records with invalid data are marked as "failed" in the results, but processing continues for all other records.

Common validation issues:

Invalid phone number formats
Missing required fields
Improperly formatted tax IDs
Invalid state/country codes

Connection Credentials

If your template includes connection credential columns, these are validated during import. Invalid credentials cause individual records to fail without stopping the overall import.

Plan Assignment Requirements

To assign a plan during import, the merchant must have valid credentials for all connections associated with that plan. Missing or invalid credentials prevent plan assignment.

Enabling Merchants

To enable a merchant during import (active = true), the merchant must:

Have a plan assigned
Have valid credentials for all plan connections

Merchants missing these requirements import successfully but remain disabled.

Step 3: Encrypt the File

Preczn requires PGP encryption for files containing sensitive data (bank accounts, credentials, PII).

Install PGP Tools

Mac: Install GPG Tools

Windows/Linux: Install GnuPG

Download Preczn's Public Key

https://core.preczn.com/tokenImportPublicKey.asc

Import the key:

gpg --import tokenImportPublicKey.asc

Encrypt Your File

gpg -r [email protected] -a -e --output merchants.csv.gpg merchants.csv

Flag	Purpose
`-r [email protected]`	Recipient (Preczn's key)
`-a`	ASCII armor output
`-e`	Encrypt
`--output`	Output filename

📘
Enrichment-Only Imports
If your import contains only non-sensitive data (no bank accounts, credentials, or PII), encryption may be skipped. Confirm with your account manager.

Step 4: Submit the File

Send your encrypted file to:

Your Preczn account manager (via Slack or email)
[email protected]

Include any relevant context about the import (e.g., expected record count, target connections).

Step 5: Review Results

Preczn sends an email notification when processing completes. The results file includes:

Column	Description
`platformUID`	Your identifier from the original file
`merchantId`	The new Preczn merchant ID (`mid_`)
`status`	Success or failure indicator
`errors`	Validation error details (if failed)

Use the platformUID to match results back to your source records.

Troubleshooting

Common Import Failures

Issue	Cause	Solution
Missing `platformUID`	Required field empty	Add unique identifier for each row
Invalid credentials	Connection credentials don't validate	Verify credentials with the connection
Plan not assigned	Missing credentials for plan connections	Add all required connection credentials
Merchant not enabled	No plan assigned	Ensure plan assignment succeeds first
Validation error	Data format doesn't match API requirements	Review error details; fix data format

Need Help?

Contact your account manager or [email protected] for assistance with:

Template requests
Data formatting questions
Import troubleshooting
Results interpretation