List Settlement Lines
GET/settlements/:id/lines
List Settlement Lines
Request
Path Parameters
ID of the settlement to list lines for
Query Parameters
Default value: 1
Page to list
Responses
- 200
- 401
- 403
- 404
- application/json
- Schema
- Example (from schema)
Schema
Array [
- payment: A successful payment or a captured transaction.
- refund: A payment that has been refunded to the payer.
- void: A canceled payment that does not incur any fees, unlike a refund.
- fee: A service fee charged by the platform for processing a payment.
- platform_duties: Additional charges taken from entity and paid to the platform.
- other_duties: Miscellaneous additional charges that do not fall into specific categories.
- chargeback: A refunded payment due to a chargeback dispute.
- chargeback_penalty: A penalty fee charged when a client loses a chargeback dispute.
- installment: A recurring payment deducted as part of a loan repayment through a partner.
- If the transaction is a purchase, then this value equals to
created_at
from the payment object. - If the transaction is a result of a capture, then
captured_at
is shown here. - If refund, then
refunded_at
is used. - If void, then
voided_at
is used. - CreditCardSource
- DevicePaymentSource
- StcPaySource
]
linesobject[]
Payment ID this line is related to
Possible values: [payment
, refund
, void
, fee
, platform_duties
, other_duties
, chargeback
, chargeback_penalty
, installment
]
The type of operation settled:
ISO-4217 three-letter currency code.
Total payment amount
Net amount settled to the merchant. This can be a negative value.
Transaction fee including TAX
VAT
Possible values: Value must match regular expression ^\d{12}$
The RRN or retrieval reference number. This is a unique number for the transaction generated by the acquirer gateway and is sent to the issuer during the authorization process.
This number is not unique across schemes (e.g. Visa and mada).
This number can be useful in tracking the payment in the card holder account statement.
Possible values: Value must match regular expression ^\d{6}$
A six-digit number returned by the issuer in response to a successful authorization process.
Payer IPv4 address. This information is collected from the connection that has created the payment.
You must ensure that the payment is created from the client device directly to ensure correct collection of the IP address.
Date and time when the transaction being settled occured.
Added for a future feature. This will be null
for now. Can be ignored when deserializing.
Added for a future feature. This will be null
for now. Can be ignored when deserializing.
sourceobject
Source response object
oneOf
Possible values: [creditcard
]
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Card holder name
Masked card number showing first six and last four digits.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [applepay samsungpay googlepay
]
This list can change as new wallet methods become available and the merchant uses them.
Possible values: [mada
, visa
, master
, amex
]
The scheme through which the payment is processed.
Masked card number showing only last four digits.
Masked card number showing first six and last four digits.
Name of the card issuing bank. This name is inferred based on the card BIN or IIN.
Origin country of the card issuer. A two-letter ISO 3166 code.
Possible values: [debit
, credit
, charge_card
, unspecified
]
Indicates the card category or product type, e.g., Platinum, Signature, etc.
This field is a human readable text and does not have a defined set of values.
Possible values: [stcpay
]
Mobile number used to authorize the STC Pay payment.
Cashier identifier sent to STC Pay during request initiation. This will show in the merchant dashboard.
Branch identifier sent to STC Pay during request initiation. This will show in the merchant dashboard.
metadataobject
A set of key-value pairs where both key and value are strings. Metadata allows you to add more information to the object that will be returned later on in responses and webhook messages. Metadata is searchable using the Payment List API.
metaobject
{
"lines": [
{
"payment_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"type": "payment",
"currency": "SAR",
"payment_amount": 25000,
"amount": 24209,
"fee": 791,
"tax": 103,
"reference_number": "433115207925",
"authorization_code": "262345",
"ip": "198.51.100.42",
"transacted_at": "string",
"splits": null,
"custom_splits": null,
"source": {},
"metadata": {
"cart_id": "72e470a5-cbc4-47b3-a52a-e89fda6adb19",
"customer_email": "[email protected]",
"customer_id": "23432"
}
}
],
"meta": {
"current_page": 1,
"next_page": null,
"prev_page": null,
"total_pages": 1,
"total_count": 1
}
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [authentication_error
]
Possible values: [Invalid authorization credentials
]
{
"type": "authentication_error",
"message": "Invalid authorization credentials",
"errors": null
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [api_error
]
Possible values: [User not authorized
]
{
"type": "api_error",
"message": "User not authorized",
"errors": null
}
- application/json
- Schema
- Example (from schema)
Schema
Possible values: [record_not_found
]
{
"type": "record_not_found",
"message": "The <object type> record you were looking for was not found.",
"errors": null
}