Reports
Bank rails & accounts
Webhook events
11min
the purpose of this document is to explain the webhook events export file drop by partner report you can use webhooks within the cross river operating system (cos) to notify you when different events occur banking and payments about webhooks glossary term description crb cross river bank partner crb’s immediate customer, i e you the table below shows the different columns included in the report together with descriptions and explanations of the information they represent column description eventid the unique id for the event eventname the name of the event status this column shows the event status, which could be pending the event has been created, but no attempt to send it has been made yet success the event was successfully sent to the registered url failed the event could not be delivered to the registered url resource refers to the resource relating to the event for example, an account that was opened createdat the date and time the event was created lastattemptedat the date and time the event was last sent partnerid the unique identification number for the partner resource event names this section describes the different webhook events you can register for where relevant, additional information is provided for some of the events customer events event name notes core customer onboarded a new customer was onboarded core customer profile changed information within a customer’s profile was changed this does not include changes to cif number, name, address, phone, identification, or email core customer name changed the customer name changed core customer cifnumber changed the customer cif number changed core customer address added a customer address was added core customer address changed a customer address was changed core customer address removed a customer address was removed core customer phone added a customer phone number was added core customer phone changed a customer phone number changed core customer phone removed a customer phone number was removed core customer identification added a customer identification was added core customer identification changed a customer identification changed core customer identification removed a customer identification was removed core customer email added a customer email address was added core customer email changed a customer email address was changed core customer email removed a customer email address was removed core customer ofac changed a customer ofac scan status was changed core customer pepscan changed a customer pep scan status was changed account events event name notes core account opened an account was opened core account status changed an account status changed core account closed an account was closed core account title changed an account title changed core account settled an account was settled core subaccount opened a sub account was opened core subaccount status changed a sub account status changed core subaccount closed a sub account was closed core subaccount title changed a sub account title was changed core relationship added a relationship was added to an account, such as a joint owner core relationship removed a relationship was removed from an account core restriction placed a restriction was placed on an account core restriction removed a restriction was removed from an account core fee assessed a fee was assessed on an account core fee waived a fee was waived on an account core interest accrued interest accrued on an account core interest paid interest was paid on an account core statement generated an account statement was generated core statementdocument attached a document (pdf) was attached to a statement record core stoppayment placed a stop payment was placed on an account core stoppayment removed a stop payment was removed from an account core regdpolicy violated a regulation d policy was violated on a savings account transaction events event name notes core transaction completed the transaction was completed successfully core transaction rejected cos was unable to complete the transaction core activity posted activity has posted to an account core memopost created a memo post was created for an account core memopost changed a memo post for an account was changed core memopost removed a memo post for an account was removed core hold placed a hold was placed on an account core hold changed a hold on an account was changed core hold removed a hold on an account was removed ach events event name notes ach payment canceled an outbound payment was canceled at the partner's request ach payment rejected an outbound payment could not be processed due to compliance reasons or failed to fund ach payment sent an outbound payment has been transmitted to the federal reserve ach payment received an inbound payment was received from another bank ach return received a previously originated payment has been returned by the receiving bank ach noc received a notification of change was sent from the receiving bank regarding a previous origination ach hold escalated a hold relating to either an inbound or outbound payment was marked for escalation by a member of the crb operations team this is used to indicate that the partner either needs to provide additional documentation or take further action rtp events event name description rtp payment sent an outbound payment was successfully sent to the receiving institution and the funds are available in the receiver's bank account rtp payment received an inbound payment has been received from another institution and has successfully posted to an account in cos rtp payment rejected payment was rejected by the receiving institution or rtp network rtp payment canceled payment was canceled at the request of the partner or a payment with a status of researchrequired has been canceled rtp payment researchrequired no response was received for an outbound payment manual research is required to determine if the payment should be completed or canceled rtp payment failed payment failed due to technical reasons rtp hold escalated a hold relating to an outbound payment was marked for escalation by a member of the crb operations team this is used to indicate that the partner either needs to provide additional documentation or take further action rtp refund requested a request has been received to refund a previously accepted credit transfer wire events event name description wire payment canceled an outbound wire was cancelled at the partner's request wire payment rejected an outbound wire could not be processed due to compliance reasons or was rejected by the federal reserve wire payment processed an outbound wire was transmitted to the federal reserve wire payment sent an outbound wire was transmitted to the federal reserve and has been successfully acknowledged an imad number is now available wire payment received an inbound wire has been received from another bank wire hold escalated a hold relating to either an inbound or outbound wire was marked for escalation by a member of the crb operations team this is used to indicate additional documentation or action is needed by the partner xpay events event name description xpay payment received an inbound payment request has been received and is awaiting approval xpay payment canceled a payment was cancelled at the sender's request or it has expired xpay payment approved payment was approved by the receiver xpay payment rejected payment was rejected by the receiver xpay payment failed payment failed to post to either the sender or receiver's account this is normally due to insufficient funds xpay payment completed payment has been posted to both the sender’s and receiver's accounts debit card events event name description debitcard card activated a card was activated successfully debitcard card underreview a card was changed to “review” status debitcard card closed a card has been permanently closed debitcard card created a card has been created and is pending activation debitcard card createfailed card creation failed debitcard card ordered a card has been ordered and will be mailed to the customer debitcard card pincreated a card pin was set for the first time debitcard card pinreset a card pin was reset debitcard card profilechanged profile data for the card (such as address) has been changed debitcard card reactivated a previously suspended card has been reactivated debitcard card replaced a lost or damaged card has been replaced debitcard card suspended a card has been suspended temporarily debitcard authorization created purchase authorization has been memo posted to the account debitcard authorization cleared purchase authorization has cleared and no further incremental changes are expected debitcard authorization changed the purchase authorization amount has changed debitcard authorization settled purchase authorization has been posted in the form of an account transaction the original memo post has been removed checks events event name description check payment sent a check deposit has been sent to the federal reserve for clearing check payment received a check drawn on an account in cos has been deposited at another bank and has been received from the federal reserve for posting check payment canceled an outbound payment has been canceled at the request of the partner check payment rejected an outbound check could not be processed either for compliance reasons or it was rejected by the federal reserve check payment returned a previously deposited check has been returned by the receiving bank