Everything is OK.
Something went wrong. Several attempts to send events to this registration failed. No further attempts will be made until registration is restarted.
We are attempting to restart this registration. An event must be successfully transmitted before the status will transition back to Active.
Events will be pushed to a partner endpoint. A 200 OK response is expected in order for it to be considered successful. (Default)
Events will be consumed by partner polling the events API periodically and calling acknowledge API method for each event successfully processed.
Events will be sent to the partner via SFTP in a CSV file once per day.
Event has been created, but no attempt to send it has been made yet.
Event was successfully delivered to the registered URL.
We could not deliver the event to the registered URL. See the event logs for more detail on the failure reason.
Webhook is delivered with an array of resource identifiers related to that event.
With this format you get everything in a 'Basic' event, in addition you will receive a 'Details' array containing various meta data pertaining to each resource. For example, on the ACH.Return.Received event you would receive the Return Code and Original Payment ID.
A new customer has been onboarded.
A customer OFAC scan status has been changed.
A customer PEP scan status has been changed.
A document (pdf) was attached to a generated statement.
A Regulation D policy was violated on a savings account.
Transaction completed successfully.
Transaction was unable to complete.
Account activity record has been posted as the result of a transaction.
Outbound payment was canceled at the partner's request.
Outbound payment could not be processed due to compliance reasons or failed to fund.
Outbound payment has been transmitted to the Federal Reserve.
An inbound payment was received from another bank.
A previously originated payment has been returned by the receiving bank.
A notification of change has been sent from the receiving bank regarding a previous origination.
A hold relating to either an inbound or outbound payment was marked for escalation by a member of the Operations team. Commonly this is used to indicate additional documentation or action is needed by the partner.
Outbound payment has been successfully sent to the receiving institution and the funds are available in the receiver's bank account.
Inbound payment has been received from another institution and has successfully posted to an account in COS.
Payment has been rejected by the receiving institution or RTP Network.
Payment was canceled at the request of the partner or a payment with a status of ResearchRequired has been canceled.
No response was received for an outbound payment, manual research is required to determine if the payment should be completed or canceled.
Payment has failed due to technical reasons.
A hold relating to either an outbound payment was marked for escalation by a member of the Operations team. Commonly this is used to indicate additional documentation or action is needed by the partner.
Request has been received to refund a previously accepted credit transfer.
Outbound wire was canceled at the partner's request.
Outbound wire could not be processed due to compliance reasons or was rejected by the Federal Reserve.
Outbound wire has been transmitted to the Federal Reserve. Still possible the wire could be rejected.
Outbound wire has been transmitted to the Federal Reserve and has been successfully acknowledged. IMAD number is now available.
Inbound wire has been received from another bank.
A hold relating to either an inbound or outbound wire was marked for escalation by a member of the Operations team. Commonly this is used to indicate additional documentation or action is needed by the partner.
Inbound payment request has been received and is awaiting approval.
Payment canceled at the sender's request or has expired.
Payment was approved by the receiver.
Payment was rejected by the receiver.
Payment failed to post to either the sender or receiver's account, most commonly due to insufficient funds.
Payment has been posted to both the sender's and receiver's accounts.
A card has been successfully activated.
A card has been changed to review status.
A card has been permanently closed.
A card has been created pending activation.
Card creation has failed.
A card has been ordered and will be mailed to the customer.
A card PIN has been set for the first time.
A card PIN has been reset.
Profile data for the card (such as address) has been changed.
A previously suspended card has been reactivated.
A lost or damaged card has been replaced.
A card has been temporarily suspended.
Purchase authorization has been memo posted to the account.
Purchase authorization has cleared and no further incremental changes are expected.
Purchase authorization amount has changed.
Purchase authorization has been posted in the form of an account transaction. The original memo post has been removed.
A check deposit has been sent to the Federal Reserve for clearing.
A check drawn on an account in COS has been deposited at another bank and has been received from the Federal Reserve for posting.
An outbound payment has been canceled at the request of the partner.
Outbound check could not be processed due to compliance reasons or was rejected by the Federal Reserve.
A previously deposited check has been returned by the receiving bank.
Details of a check have been changed.
A hold relating to either an inbound or outbound check was marked for escalation by a member of the Operations team. Commonly this is used to indicate additional documentation or action is needed by the partner.
A check's Reg CC Policy has been updated.
A check has been authorized for Positive Pay.
A check's Positive Pay status has been revoked.
A check drawn on an account in COS has been presented but was not authorized for Positive Pay.
Updated 2 months ago