Class TransactionEvent (1.14.0)

Version 1.14.0

• 1.26.0 (latest)
• 1.25.0
• 1.24.1
• 1.23.0
• 1.22.0
• 1.21.2
• 1.20.0
• 1.19.1
• 1.18.1
• 1.17.1
• 1.16.1
• 1.15.0
• 1.14.0
• 1.13.0
• 1.12.1
• 1.11.1
• 1.10.0
• 1.9.0
• 1.8.3
• 1.7.1
• 1.6.1
• 1.5.0
• 1.4.1
• 1.3.1
• 1.2.0
• 1.1.2
• 1.0.0
• 0.4.2
• 0.3.3
• 0.2.1
• 0.1.0

TransactionEvent(mapping=None, *, ignore_unknown_fields=False, **kwargs)

Describes an event in the lifecycle of a payment transaction.

Attributes
Name	Description
event_type	google.cloud.recaptchaenterprise_v1.types.TransactionEvent.TransactionEventType Optional. The type of this transaction event.
reason	str Optional. The reason or standardized code that corresponds with this transaction event, if one exists. For example, a CHARGEBACK event with code 6005.
value	float Optional. The value that corresponds with this transaction event, if one exists. For example, a refund event where $5.00 was refunded. Currency is obtained from the original transaction data.
event_time	google.protobuf.timestamp_pb2.Timestamp Optional. Timestamp when this transaction event occurred; otherwise assumed to be the time of the API call.

Classes

TransactionEventType

TransactionEventType(value)

Enum that represents an event in the payment transaction lifecycle.

Values: TRANSACTION_EVENT_TYPE_UNSPECIFIED (0): Default, unspecified event type. MERCHANT_APPROVE (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 (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 (3): Indicates that the transaction is being evaluated by a human, due to suspicion or risk. AUTHORIZATION (4): Indicates that the authorization attempt with the card issuer succeeded. AUTHORIZATION_DECLINE (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 (6): Indicates that the transaction is completed because the funds were settled. PAYMENT_CAPTURE_DECLINE (7): Indicates that the transaction could not be completed because the funds were not settled. CANCEL (8): Indicates that the transaction has been canceled. Specify the reason for the cancellation. For example, 'INSUFFICIENT_INVENTORY'. CHARGEBACK_INQUIRY (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 (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 (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 (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 (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 (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 (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 (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 (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 (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.