DynamoDB
collection-history - us-east-1
Collection Log
A record of an attempted float collection. Not specifically a payment attempt though.
Keys
-
PK - loan_id
-
SK - run_time
Attributes
-
loan_id - Matches the float/loan id
-
run_time - Epoch timestamp in nanoseconds for when the collection was attempted
-
due_date - The initial float due date in RDS
-
outcome - The outcome of the attempt
-
DEFAULTED - 90 days since the float was due
-
COMPLETED - Pinless debit was successful
-
LOWBALANCE - The user did not have a high enough balance during retry
-
ACHSENT - An ach was submitted
-
Accepted, Accepted Early - ach was cleared
-
INVALIDPLAID - Plaid item was in error state during retry balance check
-
51, 82 etc - Usio error codes for pinless debit https://api.securepds.com/2.0/documentation/#gatewayresponsecodes
-
R01, R02, etc - Nacha return codes for ach https://api.securepds.com/2.0/documentation/#achreturncodes
-
-
process - TOMORROW, TODAY6AM, MANUAL, RETRY, WEBHOOKS, Check-ach-cleared, SUPPORT
-
run_date - The run_time in YYYY-MM-DD format
-
user_id
Query Patterns
| Query | Index | Conditions |
|---|---|---|
List collection history for a float |
Primary |
loan_id = loan_id |
profiles - us-east-1
Float Profile
A record that indicates what float amounts a user can take and their float fees at that amount.
Keys
-
PK - user_id
Attributes
-
floats - A json array of float amounts, fee amounts and is_enabled flags
-
is_float_enabled - bool
Query Patterns
| Query | Index | Conditions |
|---|---|---|
Get float profile for user |
Primary |
user_id = user_id |
Bypass
A record that indicates if a user is allowed to bypass the underwriting rules. Granted by the MX team.
Keys
-
PK - user_id
Attributes
-
expiration_date - date in YYYY-MM-DD format
-
reason - MX comments, usually the date given and the initials of the agent that did
Query Patterns
| Query | Index | Conditions |
|---|---|---|
Get requirements bypass for user |
Primary |
user_id = user_id |