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.