Wire Validations & Best Practices - Lead | API Docs

Best practices to reduce wire validation exceptions.

Overview

Lead applies various validation checks on all wire transactions processed through our systems. Validations fall into two categories:

Synchronous: The API returns an immediate error response. The wire object is not created.
Asynchronous: The wire is created but subsequently rejected. A wire.rejected webhook fires when this occurs.

Important Validations

Validation Type	Best Practice	Synchronous Rejection
`parameters_invalid`	Ensure all parameters conform to the requirements outlined in the API specification.	Yes
`non_sufficient_funds`	Monitor your originating account balance before initiating wires. Ensure sufficient funds are available before submitting transfers.	Yes
`per_transaction_limit_exceeded`	Review your per-transaction limits periodically and contact Lead if your use case requires higher transaction amounts.	Yes
`account_number_incorrect`	Ensure your account numbers are shared accurately with counterparties to prevent formatting errors on incoming wires.	No
`aggregate_limit_exceeded`	Monitor your aggregate wire volume and review your limits with Lead periodically.	No
`creditor_name_mismatch`	Instruct your counterparties to use the name of the receiving entity as the creditor name when sending wires to your account numbers.	No
`creditor_address_incorrect`	Ensure that wires contain a full physical address for the creditor.	No
`regulatory_reason`	Avoid initiating wires to prohibited countries.	No

⌘I