This guide describes testing events, events that are triggered by automated processes, and events that are triggered by actions taken in the <<glossary:CST>>.

## Testing events

Most event messages that are available in the <<glossary:Production>> environment can also be tested in the <<glossary:CV>> environment. You can request to enable different events in CV and Production, allowing you to test functionality in your own system before you go live in Production.

The following events are not available for testing in the CV environment.

**Mobile wallet events**

• `AACN, GACN, SACN: mobile_activation ACN`

• `ARDP, GRDP, SRDP: mobile_activation RDP`

• `ATKC, GTKC, STKC, VTKC: mobile_activation TKC`

• `ATVD, GTVD, STVD: mobile_activation TVD`

• `ATVN, GTVN, STVN: mobile_activation TVN`

• `ATVR, GTVR, STVR: mobile_activation TVR`

• `AYLP, GYLP, SYLP: mobile_activation YLP`

• `VAPI: mobile_activation VAPI`

**ACH events**

• `ACHC: ach_credit_fail`

• `ACHR: ach_debit_fail`

• `ACRT: ach_return`

• `FACH: ach_credit_return`

📘

Note

ACH transactions cannot be tested in the CV environment, which also means that payment (`BPMT: pmt`) and adjustment (`BADJ: adj`) events for ACH transactions cannot be tested in CV. However, payment and adjustment events can be tested in CV for other types of transactions.

## Events triggered by automated processes

Some event messages in the Events API are triggered by automated processes outside of your system rather than directly as a result of your action or your customer’s action. The following tables describe events that are triggered by automated processes.

### Account events

### Authorization events

### Transaction events

## Events triggered via CST

Some Events API messages are triggered when you perform an action in the <<glossary:CST>>. The tables below list events triggered by CST processes. Most of these events can be triggered outside of the CST as well.

### Account events

### Transaction events