Check
The Check entity is a key component within our financial platform, serving as a comprehensive hub for information on check deposits. It includes vital details like images of the check (both front and back), amount, currency, status, and payor information.
Alviere's platform enhances the deposit process through its Remote Check Deposit Capture feature. This feature allows funds to be deposited into an Alviere wallet by capturing images of a cashier's check using our iOS or Android mobile applications. Integrated with Alviere's Mobile SDKs, this functionality ensures a smooth and efficient user experience.
Transactions
All activities within this module are classified as CHECK_DEPOSIT
transactions. They follow the same rigorous workflow and regulatory standards as other ledger transactions on our platform.
Processing a Check
Our system employs advanced fraud detection techniques for check deposits. Users are required to add specific text on the back of the check as per the Alviere program guidelines. Both front and back images of the check must be captured and uploaded via Alviere's API for the deposit to be processed. Any discrepancies in the images can lead to the deposit being rejected.
Service Fees
Clients have the option to impose service fees for check deposits and for providing early access to funds. For instance, a fee of $10 could be applied for early fund release.
Fee Calculation
When applying service fees for Check Deposits, only the calc_type: "DEDUCT"
is permissible. This ensures service fees are subtracted from the clearing amount, preventing negative balances in customer accounts. These fees are then automatically transferred to the client's Service Fees account.
Check statuses
The following statuses are supported:
status |
Description |
---|---|
|
This is the status of a Check once it has been submitted through the API indicating that the Check entity has been created. |
|
This status pertains to a Check in which the image has been successfully uploaded to our platform and preverified for potential cybersecurity issues. |
|
This stage represents a Check that has been canceled by our fraud teams due to account behavior prior to check processing. |
|
This status indicates the rejection of a Check based on an automated system rule. The specific reason for the error can be obtained from the |
|
This status signifies the rejection of a Check by a compliance agent following the check processing stage. The specific reasons for the rejection can be obtained from the |
|
This status signifies an approved Check that is currently pending settlement. |
|
This status represents a settled Check. |
For Checks in ERROR
status, the following status_reason
are supported:
Reason |
Description |
---|---|
|
The account number is not readable from the MICR. |
|
There is an issue with the provided amount in the check. |
|
The difference between the entered and actual check amount exceeds a predetermined limit. |
|
Poor quality or missing data on the back image of the check. |
|
The entity is on a blacklist, usually for fraudulent activity. |
|
The check appears to be blank or incomplete. |
|
The entity is on a blocklist, similar to a blacklist but often for different types of restrictions. |
|
Depositor might have tampered with the MICR. |
|
The total daily deposit amount has exceeded the user`s limit. |
|
The total number of daily transactions has exceeded the user`s limit. |
|
The check appears to be a duplicate of another that has already been processed. |
|
The check appears to be a duplicate of another that has already been processed based on information present in MICR. |
|
The check appears to be a duplicate based on primary codeline not having a check number. |
|
The check appears to be a duplicate based on secondary codeline. |
|
The check appears to be a duplicate based on secondary codeline not having a check number. |
|
Both front and back images of the check are either missing or of poor quality. |
|
Poor quality or missing front image of the check. |
|
Check deposit is attempted from a disallowed geographic location. |
|
A high-risk score based on various risk parameters, including possible fraudulent activity. |
|
Mismatch or error in the name of the financial institution on the check. |
|
The account number provided is incorrect or invalid. |
|
Some data fields on the check are incorrect or not as expected. |
|
The check document itself is invalid (e.g., torn, faded, etc., or not a check) |
|
A low-risk score that still exceeds the acceptable risk parameters. |
|
A medium-risk score based on various risk parameters. |
|
There's an issue matching the MICR codeline with the OCR codeline. |
|
Error in the Magnetic Ink Character Recognition (MICR) code of the check. |
|
The total monthly deposit amount has exceeded the user`s limit. |
|
The total number of monthly transactions has exceeded the user`s limit. |
|
The account into which the check is being deposited is newly opened and under initial observation. |
|
The user is new and under initial observation, often with lower initial limits. |
|
The system is not able to detect a routing number in the MICR. |
|
General Optical Character Recognition (OCR) error in reading the check. |
|
OCR error specifically related to the amount field on the check. |
|
OCR error specifically related to the check number. |
|
The check is too old to be processed, exceeding the acceptable time limit. |
|
Miscellaneous reasons not covered by the categories above. |
|
Error or mismatch in the payee name on the check. |
|
Conflict or error involving both the payer and payee names on the check. |
|
The check is dated for a future date. |
|
The routing number provided is incorrect or invalid. |
|
The routing number is missing from the check. |
|
The signature on the check is missing, invalid, or doesn`t match account records. |
|
An internal system error that prevents the check from being processed. |
|
The entity is on a watchlist for various reasons, which may include regulatory or compliance issues. |
|
The total weekly deposit amount has exceeded the user`s limit. |
|
The total number of weekly transactions has exceeded the user`s limit. |
For Checks in REJECTED
status, the following rejected_reasons
are supported:
Reason |
Description |
---|---|
|
Suspected fraudulent check. |
|
Unclear amount on the check. |
|
User's account is closed. |
|
Endorsement lacks required information or has fillers. |
|
Inadequate endorsement (missing or unclear signature/indications). |
|
Missing signature and mobile deposit indication. |
|
High fraud risk related to the account. |
|
User's account is frozen or blocked. |
|
No mobile deposit indication on the endorsement. |
|
Insufficient funds to cover the check. |
|
Numeric and written amounts don't match. |
|
Check is post-dated (future-dated). |
|
Unclear or missing signatures. |
|
Missing signatures (front or back). |
|
Check's date exceeds 180 days. |
|
General reason for check return. |
|
Account not found for the given account number. |
|
Check in poor condition, unrecognizable. |
|
Uncollected funds from check deposit. |
|
Check image not clear. |