This topic describes payment transactions in Rebilly. All payment transactions have a type, status, and result value. To inspect a payment transaction, see View payment transaction details.


The type value defines the type of payment transaction.

Transaction types:

  • 3ds-authentication : An authentication using 3D Secure on the payment card. This amount can be $0. This transaction type is used when a customer is adding a card to be used at a later time.
  • Authorize : Places a hold on the funds in a customer's account. An authorization is valid for seven days.
  • Capture : Collects all funds that have been previously authorized in a customer's account.
  • Credit : Adds funds to a customer's account.
  • Refund : Returns funds that had been previously collected from a customer's account.
  • Sale : collects funds from a customer's account.
  • Setup : Performs actions from a gateway account's settings, on a provided payment instrument, to prepare the instrument for later payments. This can be authorize , authorizing and voiding or Strong Customer Authentication (SCA).
  • Void : Reverses an authorization, capture, or sale transaction. A void can only occur before settlement, otherwise a refund must be used to credit the customer.


This status value defines execution status of a payment transaction.

  • Pending: Transaction has been created and is queued.
  • Sending: Request is sent to a payment gateway.
  • Completed: Transaction is completed.

Successful payment transaction flow

The following is a successful payment transaction status flow.


Error and additional processing statuses

If a transaction does not receive a response from the payment gateway, or if there is a long delay in the response, one of the following statuses is returned:

  • Timeout: Transaction was not completed within the payment gateway account timeout period. To configure gateway account timeout, see Advanced gateway configuration .
  • Conn-err: Transaction was not completed due to a connectivity issue.
  • Never-sent: The request was not sent.
  • Waiting-capture: Transaction is approved with an authorization, the funds will be captured at some point in the future.
  • Waiting-approval: Transaction requires further action from the customer before it is marked as completed.
  • Waiting-gateway: Awaiting an approval notification from the payment gateway before the transaction is marked as completed.
  • Offsite: Transaction initiated. The customer has been redirected to a third-party website to complete the transaction,.

Additional action statuses

When a transaction is successfully completed, additional interactions can be completed that add to the transaction status.

  • Voided: Transaction authorization, capture, or sale transaction is reversed.
  • Partially-refunded: Transaction amount was partially refunded.
  • Refunded: Transaction amount was fully refunded.
  • Disputed: Transaction, or transaction amount, is disputed by the merchant or customer.


The result value defines the end result of a payment transaction.

  • Abandoned: The customer did not complete the transaction within the Time To Live (TTL) window. To configure the payment gateway TTL window, see Advanced gateway configuration .
  • Approved: Transaction is approved by the payment gateway and payment is processed.
  • Canceled: Transaction was canceled by the merchant, or by an automation, such as a blocklist match.
  • Declined: Customer explicitly canceled the transaction.

To inspect a payment transaction, see View payment transaction details.

Payment gateway response codes and messages

The payment gateway response contains a response code and message which describe the transaction. For example, if a transaction is declined, the message may contain information about why the transaction was declined. To view payment gateway response codes and messages, see View payment transaction details.

In Rebilly, the code and message received from the payment gateway is displayed in the "Original message" and "Original code" fields.

Rebilly uses a superset of the ISO 8583 — international standard for financial transaction card originated interchange messaging. The gateway code is mapped to ISO 8583 as part of the gateway integration process. The standardized codes are displayed in the "Message" and "Code" fields. This standardized coding enables you to use the same response codes and messages across all payment gateway integrations.