Documentation

Column allows customers to programmatically return checks issued at Column. Checks deposited at Column cannot be returned by Column customers - they can only be returned at the issuing bank.

Issued Check Returns

Checks are returned for a variety of reasons, most commonly for insufficient funds in the payer's account. Column requires customers prefund an account prior to issuing checks, thus preventing NSF returns. For most return reasons, a BOFD may attempt to re-clear the check. If re-cleared by the BOFD, the check can be returned a second time. Thus, a single check transfer can have multiple returns associated with it.

User Initiated Returns

A check payer has the ability to initiate a check return after the check has successfully cleared (in settled status) if the check was not authorized (return reason Q) or is suspected counterfeit (return reason N). Column will hold the returned fund for 2 days in case the return gets dishonored.

Column Auto-Returns

Column will automatically return checks for a number of reasons including check number not found, positive-pay mismatch, and account number not found. Column will also automatically return checks that have stop payment instructions.

Deposited Check Returns

Checks deposited at Column can be returned by the issuing bank. If a check is returned with return reason A (NSF) or return reason B (UCF - Uncollected Funds Hold), Column will automatically attempt to reclear the check. If a reclear attempt succeeds, Column will mark a check settled. If a reclear attempt fails, Column will mark a check returned. For all other return codes, Column will immediately mark a check returned without a reclear attempt.

Valid Return Codes

Notifications and States

When a check transfer is returned, Column creates a check return object. Check return objects do not have webhooks, as events are mapped to those on the check transfer object. Below are the states a check return object may go through.