This resource represents the transaction event that has happened in your account.
Sample TransactionJSON
API Index URL
Transactions attributes
The payment method of this transaction
Card
Cash
Check
Only applicable for a transaction of type
= refund.
This value is set by Chargebee when an automated chargeback
occurs. You can also set this explicitly when recording a refund
.
Bank Transfer
The reference number for this transaction. For example, the check number when payment_method
= check
.
Gateway through which this transaction was done. Applicable only for 'Card' Payment Method
Chargebee test gateway.
Chargebee Payments gateway
Adyen is a payment gateway.
Stripe is a payment gateway.
WePay is a payment gateway.
Type of the transaction.
The transaction represents an authorization for capturing the amount
from the customer's payment_source
.
The transaction represents capture of amount
from the customer's payment_source
.
The transaction represents a refund of amount
to the customer's payment_source
.
Indicates a reversal transaction.
The status of this transaction.
Transaction is being processed by the gateway. This typically happens for direct debit transactions or, in case of cards, refund transactions. Such transactions can take 2-7 days to complete, depending on the gateway and payment method.
The transaction is successful.
The transaction got voided or authorization expired at gateway.
Transaction failed. Refer the 'error_code' and 'error_text' fields to know the reason for failure
Transaction failed because of Gateway not accepting the connection.
When connection with the Gateway gets terminated abruptly. For needs_attention
status Chargebee automatically reconcile the transaction for few gateways, for rest of the gateways you have to use the Reconcile transaction API.
You can use this API to update the id_at_gateway
(Gateway Transaction ID) and status
for a needs_attention
transaction to be reconciled at par with the gateway.
Learn more
about needs_attention
transaction status
Indicates that a successful payment transaction has failed now due to a late failure notification from the payment gateway, typically caused by issues like insufficient funds or a closed bank account.
Indicates whether or not the transaction has been identified as fraudulent.
The transaction has been marked as safe
The transaction has been identified as potentially fraudulent by the gateway
The transaction has been marked as fraudulent
Type of authorization transaction.
The transaction has been created to block the funds from payment method.
The transaction has been created for payment method verification.
The transaction was authorized in advance for capture at a later time by a scheduled system job. The capture may succeed or fail, and its outcome is recorded as a linked transaction under linked_payments
.
This is the part of the amount
which has not been invoiced yet and is therefore added to excess_payments
for the customer. Applicable only for a transaction of type
= payment
.
A unique id used to track this transaction across various systems you integrate with. This id is passed to the payment gateway when the transaction is initiated. Supported only for the Exact payment gateway .
The unique ID of the business entity
of this transaction.
This is always the same as the business entity of the customer.
Comprehensive information regarding the error experienced during an unsuccessful or declined transaction. Learn more about gateway error references