Reference documentation and code samples for the reCAPTCHA Enterprise V1 API module Google::Cloud::RecaptchaEnterprise::V1::TransactionEvent::TransactionEventType.
Enum that represents an event in the payment transaction lifecycle.
Constants
TRANSACTION_EVENT_TYPE_UNSPECIFIED
value: 0 Default, unspecified event type.
MERCHANT_APPROVE
value: 1 Indicates that the transaction is approved by the merchant. The
accompanying reasons can include terms such as 'INHOUSE', 'ACCERTIFY',
'CYBERSOURCE', or 'MANUAL_REVIEW'.
MERCHANT_DENY
value: 2 Indicates that the transaction is denied and concluded due to risks
detected by the merchant. The accompanying reasons can include terms such
as 'INHOUSE', 'ACCERTIFY', 'CYBERSOURCE', or 'MANUAL_REVIEW'.
MANUAL_REVIEW
value: 3 Indicates that the transaction is being evaluated by a human, due to
suspicion or risk.
AUTHORIZATION
value: 4 Indicates that the authorization attempt with the card issuer succeeded.
AUTHORIZATION_DECLINE
value: 5 Indicates that the authorization attempt with the card issuer failed.
The accompanying reasons can include Visa's '54' indicating that the card
is expired, or '82' indicating that the CVV is incorrect.
PAYMENT_CAPTURE
value: 6 Indicates that the transaction is completed because the funds were
settled.
PAYMENT_CAPTURE_DECLINE
value: 7 Indicates that the transaction could not be completed because the funds
were not settled.
CANCEL
value: 8 Indicates that the transaction has been canceled. Specify the reason
for the cancellation. For example, 'INSUFFICIENT_INVENTORY'.
CHARGEBACK_INQUIRY
value: 9 Indicates that the merchant has received a chargeback inquiry due to
fraud for the transaction, requesting additional information before a
fraud chargeback is officially issued and a formal chargeback
notification is sent.
CHARGEBACK_ALERT
value: 10 Indicates that the merchant has received a chargeback alert due to fraud
for the transaction. The process of resolving the dispute without
involving the payment network is started.
FRAUD_NOTIFICATION
value: 11 Indicates that a fraud notification is issued for the transaction, sent
by the payment instrument's issuing bank because the transaction appears
to be fraudulent. We recommend including TC40 or SAFE data in the
reason field for this event type. For partial chargebacks, we recommend
that you include an amount in the value field.
CHARGEBACK
value: 12 Indicates that the merchant is informed by the payment network that the
transaction has entered the chargeback process due to fraud. Reason code
examples include Discover's '6005' and '6041'. For partial chargebacks,
we recommend that you include an amount in the value field.
CHARGEBACK_REPRESENTMENT
value: 13 Indicates that the transaction has entered the chargeback process due to
fraud, and that the merchant has chosen to enter representment. Reason
examples include Discover's '6005' and '6041'. For partial chargebacks,
we recommend that you include an amount in the value field.
CHARGEBACK_REVERSE
value: 14 Indicates that the transaction has had a fraud chargeback which was
illegitimate and was reversed as a result. For partial chargebacks, we
recommend that you include an amount in the value field.
REFUND_REQUEST
value: 15 Indicates that the merchant has received a refund for a completed
transaction. For partial refunds, we recommend that you include an amount
in the value field. Reason example: 'TAX_EXEMPT' (partial refund of
exempt tax)
REFUND_DECLINE
value: 16 Indicates that the merchant has received a refund request for this
transaction, but that they have declined it. For partial refunds, we
recommend that you include an amount in the value field. Reason
example: 'TAX_EXEMPT' (partial refund of exempt tax)
REFUND
value: 17 Indicates that the completed transaction was refunded by the merchant.
For partial refunds, we recommend that you include an amount in the
value field. Reason example: 'TAX_EXEMPT' (partial refund of exempt
tax)
REFUND_REVERSE
value: 18 Indicates that the completed transaction was refunded by the merchant,
and that this refund was reversed. For partial refunds, we recommend that
you include an amount in the value field.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[],[],null,["# reCAPTCHA Enterprise V1 API - Module Google::Cloud::RecaptchaEnterprise::V1::TransactionEvent::TransactionEventType (v1.8.0)\n\nVersion latestkeyboard_arrow_down\n\n- [1.8.0 (latest)](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/latest/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.7.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.7.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.6.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.6.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.5.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.5.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.4.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.4.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.3.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.3.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.2.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.2.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.1.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.1.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [1.0.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/1.0.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.22.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.22.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.21.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.21.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.20.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.20.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.19.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.19.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.18.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.18.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.17.3](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.17.3/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.16.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.16.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.15.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.15.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.14.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.14.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.13.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.13.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.12.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.12.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.11.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.11.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.10.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.10.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.9.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.9.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.8.0](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.8.0/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType)\n- [0.7.1](/ruby/docs/reference/google-cloud-recaptcha_enterprise-v1/0.7.1/Google-Cloud-RecaptchaEnterprise-V1-TransactionEvent-TransactionEventType) \nReference documentation and code samples for the reCAPTCHA Enterprise V1 API module Google::Cloud::RecaptchaEnterprise::V1::TransactionEvent::TransactionEventType.\n\nEnum that represents an event in the payment transaction lifecycle.\n\nConstants\n---------\n\n### TRANSACTION_EVENT_TYPE_UNSPECIFIED\n\n**value:** 0 \nDefault, unspecified event type.\n\n### MERCHANT_APPROVE\n\n**value:** 1 \nIndicates that the transaction is approved by the merchant. The\naccompanying reasons can include terms such as 'INHOUSE', 'ACCERTIFY',\n'CYBERSOURCE', or 'MANUAL_REVIEW'.\n\n### MERCHANT_DENY\n\n**value:** 2 \nIndicates that the transaction is denied and concluded due to risks\ndetected by the merchant. The accompanying reasons can include terms such\nas 'INHOUSE', 'ACCERTIFY', 'CYBERSOURCE', or 'MANUAL_REVIEW'.\n\n### MANUAL_REVIEW\n\n**value:** 3 \nIndicates that the transaction is being evaluated by a human, due to\nsuspicion or risk.\n\n### AUTHORIZATION\n\n**value:** 4 \nIndicates that the authorization attempt with the card issuer succeeded.\n\n### AUTHORIZATION_DECLINE\n\n**value:** 5 \nIndicates that the authorization attempt with the card issuer failed.\nThe accompanying reasons can include Visa's '54' indicating that the card\nis expired, or '82' indicating that the CVV is incorrect.\n\n### PAYMENT_CAPTURE\n\n**value:** 6 \nIndicates that the transaction is completed because the funds were\nsettled.\n\n### PAYMENT_CAPTURE_DECLINE\n\n**value:** 7 \nIndicates that the transaction could not be completed because the funds\nwere not settled.\n\n### CANCEL\n\n**value:** 8 \nIndicates that the transaction has been canceled. Specify the reason\nfor the cancellation. For example, 'INSUFFICIENT_INVENTORY'.\n\n### CHARGEBACK_INQUIRY\n\n**value:** 9 \nIndicates that the merchant has received a chargeback inquiry due to\nfraud for the transaction, requesting additional information before a\nfraud chargeback is officially issued and a formal chargeback\nnotification is sent.\n\n### CHARGEBACK_ALERT\n\n**value:** 10 \nIndicates that the merchant has received a chargeback alert due to fraud\nfor the transaction. The process of resolving the dispute without\ninvolving the payment network is started.\n\n### FRAUD_NOTIFICATION\n\n**value:** 11 \nIndicates that a fraud notification is issued for the transaction, sent\nby the payment instrument's issuing bank because the transaction appears\nto be fraudulent. We recommend including TC40 or SAFE data in the\n`reason` field for this event type. For partial chargebacks, we recommend\nthat you include an amount in the `value` field.\n\n### CHARGEBACK\n\n**value:** 12 \nIndicates that the merchant is informed by the payment network that the\ntransaction has entered the chargeback process due to fraud. Reason code\nexamples include Discover's '6005' and '6041'. For partial chargebacks,\nwe recommend that you include an amount in the `value` field.\n\n### CHARGEBACK_REPRESENTMENT\n\n**value:** 13 \nIndicates that the transaction has entered the chargeback process due to\nfraud, and that the merchant has chosen to enter representment. Reason\nexamples include Discover's '6005' and '6041'. For partial chargebacks,\nwe recommend that you include an amount in the `value` field.\n\n### CHARGEBACK_REVERSE\n\n**value:** 14 \nIndicates that the transaction has had a fraud chargeback which was\nillegitimate and was reversed as a result. For partial chargebacks, we\nrecommend that you include an amount in the `value` field.\n\n### REFUND_REQUEST\n\n**value:** 15 \nIndicates that the merchant has received a refund for a completed\ntransaction. For partial refunds, we recommend that you include an amount\nin the `value` field. Reason example: 'TAX_EXEMPT' (partial refund of\nexempt tax)\n\n### REFUND_DECLINE\n\n**value:** 16 \nIndicates that the merchant has received a refund request for this\ntransaction, but that they have declined it. For partial refunds, we\nrecommend that you include an amount in the `value` field. Reason\nexample: 'TAX_EXEMPT' (partial refund of exempt tax)\n\n### REFUND\n\n**value:** 17 \nIndicates that the completed transaction was refunded by the merchant.\nFor partial refunds, we recommend that you include an amount in the\n`value` field. Reason example: 'TAX_EXEMPT' (partial refund of exempt\ntax)\n\n### REFUND_REVERSE\n\n**value:** 18 \nIndicates that the completed transaction was refunded by the merchant,\nand that this refund was reversed. For partial refunds, we recommend that\nyou include an amount in the `value` field."]]
