Manage an account

deposit, withdraw, transfer deposits, withdrawals and transfers can be understood as being part of a transaction in the cross river operating system (cos) a transaction always involves a debit of one account (withdrawal) and a credit of another account (deposit), completed as a single atomic (simple) operation both sides of the transaction must happen for it to be considered completed if, for example, the debit account does not have enough money to cover the transaction, the credit operation will not complete this makes sure that accounts are never out of balance and makes tracking where the money is much easier once you've opened an account, use our payment apis to send and receive funds between banks via ach , instant payments , wires , international payments or checks you can also use instant payments to tranfer funds within cross river, with our payment networks option account activity record when a deposit, withdrawal, or transfer is made, we update the account to show this activity we call this an activity record this ensures that the account balance is accurate and reflects all the money going in and out of the account it's similar to updating a digital ledger to keep track of all your financial transactions a newly created activity record has a pending status until the posting day closes during the nightly settlement process at this point, cos reorders the account activity records for statement purposes as described in your deposit account agreement cos assigns a posting sequence number to each account activity record and changes the status to posted once this is done, the activity is considered final and is not updated further the order of account activity presented on a given date is not necessarily the order that each activity happened for each deposit account cross river provides a monthly account statement the statement contains all posted activity inclusive of the period start and end dates the statement lists details according to the posting sequence of the account activity records the document is retrievable as a pdf file post types in banking, a "post" refers to the process of recording a transaction in your account there are several types of posts memo posts think of a memo post as a temporary transaction it tells the system something about the account—usually that some money will be coming in or going out a memo post is applied only to one side of a transaction and may or may not affect the account available balance a memo post might stay on an account for many days when it expires it is removed and, as applicable, the information in it becomes a posted transaction activity record for example, when you pay for gas with a debit card, cos puts a memo post on the account until the transaction completes when the charge is captured and finalized, the memo post is removed and converted to a posted transaction activity record, showing the actual amount spent at the gas station an example of an "informational" memo post is with an inbound ach credit when cross river receives an instruction from the federal reserve about an inbound ach credit, we put a memo post on the account right away even though the effective date of the actual transfer might not be until the following day the job of this memo post is to tell the account holder that there is going to be some change to their account in the future you can accounts, cards and payment events for account management webhook events , including memo post webhook events a webhook event tells you the activity status posted transactions availability schedules certain credit transactions post with an availability schedule these schedules give instructions about the amount of the full transaction that will be available on each day after posting these days until all the funds are available are also called the clearing window the schedule appears on both the transaction and account activity records it appears as a array (list) of dollar amounts, where each element of the array represents a posting day for example, the following illustrates how an ach pull transaction may look with a 2 day clearing schedule (lines 15 18) availability schedule example { "id" "e25ff690 be93 469f 9915 aa9a011defbf", "transactionid" "c93978d3 3451 40a0 be01 aa9a011dec98", "tracenumber" "t192111321017433a", "status" "pending", "transactiontype" "credit", "activitytype" "external", "source" "transaction", "masteraccountnumber" "2058112745", "subaccountnumber" "2058112745", "transactioncode" "outgoing ach", "description" "test ach pull ppd id 123 ref a211p3hvg7ki", "rail" "ach", "railid" "payment/eec1b00b fcaf 4e91 a894 aa9a011d9366", "schedule" \[ 0, 0, 2700 ], "isclearing" true, "amount" 2700, "productid" "3c6d97f2 2666 44d9 b25d a9a800d6c59d", "partnerid" "d6b4c661 b38a 46a3 8963 a9a40131eacf", "postingdate" "2019 07 30t00 00 00 04 00", "executedat" "2019 07 30t13 21 01 04 00", "createdat" "2019 07 30t13 21 03 04 00", "lastmodifiedat" "2019 07 30t13 21 03 7929693 04 00" } the ach payment is for $27 00 total the schedule attribute shows that $0 will be available immediately on day 1 and that also nothing will be available on day 2 on day 3 the full $27 00 is available items such as checks generally make partial funds available each day while the item clears money amounts in api calls and responses are written without a decimal point between the dollars and the cents in addition to the schedule attribute, for convenience the response includes an isclearing flag to show whether the item is still within the clearing window in the above example, the flag switches to false on 8/1 the schedule is enforced via one or more account holds relating to the item in clearing, correlated by the railid field for example, the schedule above would be held as follows hold example { "id" "866d8cde e7cf 4bf3 897b aa9a014d9b08", "masteraccountnumber" "2058112745", "subaccountnumber" "2058112745", "status" "active", "reason" "availability", "rail" "ach", "railid" "payment/eec1b00b fcaf 4e91 a894 aa9a011d9366", "amount" 2700, "createdat" "2019 07 30t16 14 37 04 00", "expiresat" "2019 07 31t00 00 00 04 00", "partnerid" "d6b4c661 b38a 46a3 8963 a9a40131eacf", "lastmodifiedat" "2019 07 30t16 14 37 287877 04 00" } note that the hold expires at the close of business on 7/31, thus making the $27 00 available starting on the 8/1 posting day interest accrual is not affected by availability schedules accrual will continue to start on the date of the credit regardless of any holds which are in place restrictions restrictions provide a mechanism to block certain transaction activity on an account for example, if you wanted to block all ach activity on an account, you could add a restriction which only applies to the ach rail if you then wanted to entirely freeze an account, where all activity was blocked, you could add a restriction which applies to all rails partner vs internal restrictions as the name suggests, a partner restriction is one that is applied by a partner user it is visible to all users and can be modified by both partner and internal users by contrast an internal restriction is one that is visible to partner users, but cannot be modified or removed by them for example, an internal operations team member may apply an internal account freeze if they do not want it to be modified by the partner this division between partner restrictions and internal restrictions also applies to holds important should i display restrictions to my customers? restrictions and holds may be sensitive in nature your integration manager (im) will assist you with your questions on how best to handle customer support issues arising from restrictions or holds restriction policies restriction policies are managed at the product level and define the types of transactions allowed for the program as a whole account level restrictions can be applied in addition to these these policies are not managed by the partner and are configured by the integration team for your product creating restrictions account restrictions work by defining a set of criteria in which the restriction applies to for example, if we wanted to block all ach debits over $100 to an account we would create a restriction like this post https //sandbox crbcos com/core/v1/dda/accounts/200012345/restrictions { "subaccountnumber" null, "appliesto" "all", "rail" "ach", "transactiontype" "debit", "otheraccounttype" null, "amountthreshold" 10000, "transactioncode" null, "reason" "restricted", "notes" "optional notes here" } null values indicate a wildcard that any value would match posting exceptions a posting exception is like an account activity record, except it only happens when one side of a transaction fails authorization for example, if the debit side of a transaction fails due to insufficient funds in the account, cos creates a posting exception record on that account cos does not put a posting exception on the credit side of the transaction because it did not fail in this example update details sometimes even after you open a bank account, you need to add or update details of the account holder customer record you can update the account holder address, phone number and email you can also add details to the customer record about an id document for that account holder for every record, you can have multiple addresses and so forth, but you designate one of each as the primary detail for example you have a primary address and phone number among other purposes, these details are important for identity verification to fight fraud and money laundering see our customer record management customer management and customer management to learn how to update or add this information