New Features

External ID Validation

• Merchant External IDs (ex. VSP's Customer IDs) will now be validated to ensure that the same ID isn't used across multiple merchants.
• This value must be unique per merchant across the same mode (testMode or liveMode). If a merchant already exists with the same externalId in the same mode, the request will be rejected.
• Validation occurs when creating or updating external IDs via:
  • API
  • Dashboard
  • Bulk CSV Imports

❗️

Review Implementation

After the release, if your API request includes an external ID that is already in use by another merchant, the Preczn API will return a 409 error including the merchant that already has the externalID assigned.
Please ensure that externalIDs are unique per merchant. If you require assistance deduplicating merchant records, please contact Preczn Support.

📘

Existing Merchants with Duplicate External IDs

Please make note that if there are existing duplicate External IDs, there are no ill effects. However, going forward all merchants should have a unique external ID.

Session Endpoint

• A new session endpoint is now available to issue session tokens for authentication purposes. Currently, this is only supported on the following Preczn Javascript Clients:
  • Preczn Jaris B2B Lending Client
• Session tokens have a fixed 15-minute expiration. Additional configuration is under consideration for future releases.

Vault - MCC Display and Filtering

• The merchant vault can now be configured to display MCCs
• Merchants can be filtered by MCC as well

Card-on-File Flag Mapping to Processors

• You can now optionally specify how a stored card is being used when processing a transaction. The new tokenUsage field in the Process Transaction helps identify whether the charge is customer-initiated, merchant-initiated, recurring, or installment-based. This helps processors apply the correct logic and rules for card-on-file transactions.
• See the detailed documentation here: Card On File Flags

Improvements

Jaris - B2B Lending

• For details on the following updates, please review our Jaris Guide.
  • Preczn Jaris Client now uses session tokens for authentication.
    • Session tokens are created server-side using the Create Client Session endpoint.
  • Additional Statuses have been added for various application states.
  • Loan principle and remain balances are now available once the Jaris has reached a loan state.