Enums
LoanStatusEnum
These enums communicate the status of a loan.
|
Enums |
Enum number |
Description |
|---|---|---|
Received
|
1 |
Arix received a new loan application. Send attachments as the next step in the process. |
|
|
2 |
All required documents were received |
|
|
3 |
Loan successfully passed compliance |
|
|
4 |
Loan was approved for funding |
|
|
5 |
At least 1 rail was submitted for funding |
|
|
6 |
Full loan amount was funded |
|
|
7 |
An internal CR process. Confirms that account entries are complete. |
|
|
8 |
Loan finished the seasoning period and is ready to be sold |
|
|
9 |
Loan was sold (not in use) Sale info is on the post-purchase report in SFTP |
|
|
10 |
Loan was paid back by end user (not in use) |
|
|
11 |
All compliance rules were passed and the system is waiting for the funding information. Once in this status, only a |
|
|
80 |
A return/ cancel has been requested, and the funding is being returned to the originating account. |
|
|
90 |
Internal status Loan was canceled or fully returned and accounting entries were reversed. |
|
|
100 |
Issuing bank canceled the loan. Terminal State |
|
|
101 |
Loan failed the compliance check |
|
|
102 |
Issuing bank didn't approve - possible only prior to funding. Terminal State. |
|
|
103 |
All rails that were successfully funded came back as returned |
|
|
104 |
Funding was attempted, but a balance remains to be funded |
FundingResult enums
These enums communicate the results of a funding attempt.
|
Enums |
Enum number |
Description |
|---|---|---|
|
|
0 |
All funded |
|
|
1 |
Some funds were sent successfully, but some failed |
|
|
2 |
Funding failed and nothing was funded |
RailResultType enums
These enums communicate the results of a rail transaction as part of the funding attempt.
|
Enums |
Enum number |
Description |
|---|---|---|
|
|
0 |
Rail wasn't attempted |
|
|
1 |
API call was successful and the funds are pending transmission |
|
|
2 |
Full requested amount has been funded and released on the rail. Note: There is lag time between the time an ACH is sent and when it is received (by the receiving bank), usually 1 business day (unless it was sent as a same-day ACH). CR considers the rail a success if and until we receive a notice from the receiving bank that the rail failed. At that time, the status of the rail changes from Success to Returned. |
|
|
3 |
The request to fund failed immediately upon request (usually due to a mistake in the API instructions.) |
|
|
4 |
The rail was rejected |
|
|
5 |
The rail that was sent and marked as success was returned. |
|
|
6 |
A rail was skipped. No need to reattempt the funding. |
|
|
7 |
The rail failed because it couldn't be validated |
|
|
8 |
Arix received a notification that a specific ACH rail was rejected (Internal Ops) |
|
|
9 |
CR Ops canceled the ACH payment (Internal Ops) |
|
|
10 |
A Notice of Change (NOC) was received. Relevant for recurrent disbursements. (Internal Ops) Contact customer for updated instructions. |
|
|
11 |
CR Ops put the ACH transaction on hold (Internal Ops) |
|
|
12 |
COS Core (part of XPay) transaction was completed successfully (Internal Ops) |
|
|
13 |
COS Core (part of XPay) transaction was unable to complete |
|
|
15 |
Inbound payment request has been received and is awaiting approval (Internal Ops) |
|
|
16 |
Payment canceled at the sender's request or has expired |
|
|
17 |
Payment was rejected by the receiver (Internal Ops)
|
|
|
18 |
Payment failed to post to either the sender or receiver's account. |
|
|
19 |
Payment has been posted to both the sender and receiver's accounts (Internal Ops) |
|
|
20 |
COS Core (part of XPay) reversal transaction has been completed (Internal Ops) |
|
|
24 |
COS XPay requested reversal hasn't been approved (Internal Ops) |
|
|
25 |
COS XPay requested reversal was unable to be reversed (Internal Ops) |
|
|
26 |
COS XPay reversal was canceled (Internal Ops) |
|
|
27 |
Check was cashed |
|
|
28 |
Check was printed |
|
|
29 |
A digital check was printed |
|
|
30 |
The check was mailed |
|
|
31 |
The check wasn't able to be cashed |
|
|
32 |
Rail was cancelled |
RailType enums
These enums communicate the type of rail used to make the transactions.
|
Enums |
Enum number |
Description |
|---|---|---|
|
|
4 |
RPPS rail |
|
|
7 |
No funding |
|
|
8 |
Next day funding via ACH |
|
|
9 |
Same day funding via ACH |
|
|
10 |
Internal transfer between CR accounts |
|
|
20 |
Adjustments to a loan after it was funded |
|
|
30 |
Physical check |
|
|
40 |
Real Time Payments |
|
|
50 |
Card |
Wire
|
60 |
Wire |
RPPS enums
RPPS uses enums to return funding attempt results.
|
Enum name |
Enum number |
Description |
|---|---|---|
|
|
1 |
The funding attempt was received by RPPS |
|
|
2 |
The funding attempt was submitted by RPPS |
|
|
3 |
The funding attempt is pending |
|
|
4 |
The funding attempt was approved by RPPS |
|
|
5 |
The funding attempt was rejected by RPPS |
|
|
6 |
The funding attempt failed in RPPS |
|
|
7 |
The rail was returned by RPPS |
