When dealing with payments, it is crucial to differentiate between an order and a transaction as they have distinct meanings and implications.
An order is essentially a customer’s request to purchase goods or services, which serves as a record of a planned purchase. In Solidgate, an order and its associated transaction go through different stages, each of which helps move through the payment processing steps, from initiation and verification to the final state - approval, rejection, or settlement.
The card orders report provides comprehensive insights into transaction processing and customer data, allowing merchants to optimize financial tracking and operational strategies. reporting solution to deliver detailed transaction data for card orders. This tool enables tracking order statuses, managing reconciliation, and gaining actionable insights into customer behavior.
Order status
Value | Final state | Description |
---|---|---|
created | No | This is an order's initial state, indicating its creation. It remains in this state until a payment attempt occurs. |
processing | No | An order enters this state when payment is first attempted and stays here until payment is captured. |
3ds_verify | No | This state is for orders undergoing 3D Secure verification, either triggered by a payment request with a 3D parameter or additional verification by Solidgate or the issuing bank. |
auth_ok | No | Indicates successful reservation of funds for the transaction. |
auth_failed | Yes | This state indicates a failure in reserving funds. |
void_ok | Yes | The reservation of funds has been voided. |
approved | Yes | The order is approved, and the payment is successfully processed. |
declined | Yes | The order was declined. |
settle_ok | Yes | Reserved funds have been successfully captured. |
partial_settled | Yes | A portion of the funds has been captured. |
refunded | Yes | Funds by the order were
The refund involves coordination between the merchant, Solidgate, and the acquirer for successful processing. transferred back to the cardholder. |
The final state denotes whether an order can remain in that state until subsequent actions such as void or refund, as part of logical system processing. |
Transaction status
Value | Description |
---|---|
created | The transaction was created. |
processing | The transaction is currently undergoing processing. |
verify | The transaction is undergoing 3DS verification, and the customer should be redirected to the ACS URL provided to finalize the payment. |
success | The transaction has been successfully processed. |
fail | The transaction has been rejected. Refer to the
Understand why the payment is declined and how you can resolve it. error code for additional information. |
Transaction type
Value | Description |
---|---|
pay | The operation of charging includes authorization and capture in a single transaction. |
recurring | The operation of executing payments using a token for repeated transactions. |
recurring-auth | The operation of reserving funds using a token. |
refund | The operation of transferring funds back to the cardholder. |
resign | The operation of executing payments using a token in conjunction with CVV. |
resign-auth | The operation of reserving funds using a token and CVV. |
auth | The operation of reserving funds. |
settle | The operation of settling reserved funds. |
void | The operation of cancelling a reserved fund. |
apple-pay | The charge via Apple Pay. |
google-pay | The charge via Google Pay. |
Webhooks
Subscribe for events on your Solidgate account so your integration can automatically trigger actions. Webhooks notify merchants in real-time about card order status Webhook changes, such as refund , void , and settle types.
Receive notifications when network token created Webhook or network token updated Webhook by Visa or Mastercard. Real-time alerts for chargeback Webhook , prevent alert Webhook , and fraud alert Webhook allow to manage risk effectively.