Get Payment Order

🔒

Requires read_finance access scope.

The Get Payment Order API retrieves detailed information about a specific payment order. This enables users to review payment details, including status, amount, associated customer, and transaction history.

This API is especially useful for:
1. Verifying payment order details for auditing or reporting.
2. Troubleshooting payment issues with specific orders.
3. Displaying order-specific payment data in custom applications or dashboards.

Request Parameters

Public Request Parameters

📘

Public Request Parameters

Path Parameters

FieldTypeRequiredExampleDescription
idstringYespy_2oFAVxHstl9rUnique identifier of the payment order.

Response Explanation

Public Response Parameters

📘

Public Response Parameters

Successful Response

FieldTypeExampleDescription
codestringSuccessResponse status code.
messagestringSuccessResponse message.
dataobject-Contains the payment order details.
data.payment_order.idstringpy_2oFAVxHstl9rUnique ID of the payment order.
data.fee_detailsobject-Object containing fee details.
fee_details.trans_fee_amountstring"0.35"Transaction fee amount.
fee_details.fee_currencystringusdCurrency for the transaction fee.
fee_details.foreign_settlement_feestring"0.02"Fee for foreign currency settlement.
data.created_atinteger1739454978Timestamp when the order was created.
data.finished_atinteger1739454982Timestamp when the order was completed.
data.payment_statusstringsucceededStatus of the payment.
data.payment_methodstringcardPayment method used for the transaction.
data.card_brandstringcard:visaBrand of the card used.
data.pay_currencystringusdCurrency used for the payment.
data.pay_amountstring1.50Payment amount.
data.converted_amountstring1.50Amount converted into the target currency.
data.reserve_amountstring"0.30"Reserve amount for holding funds to cover potential adjustments or risks.
data.order_idstring307899-00001207Related order ID associated with the payment.

Error Response

Error responses in the API can be represented using two different fields: errors and error. Both fields provide details about issues encountered during request processing. Below is an explanation of the fields with their respective examples and descriptions.

FieldTypeDescriptionExample
codestringThe error code indicating the type of issue.InvalidParameter
messagestringA detailed message describing the error.wrong cursor
FieldTypeExampleDescription
errorString "store is not active"Indicates an error encountered during the process

Error Detail

Status CodeMessagePossible ReasonExample Response
400Bad RequestInvalid input format or request structure (e.g., missing required fields or incorrect data types).Bad Request
UnauthorizedThe request is missing valid authentication credentials or the credentials provided are invalid.Unauthorized
500UnknownErrorinvalid or empty id input"Unknown error, please contact shoplazza technical support to resolve the issue."

API Structure Overview

Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!