GET
Get Payment Request Status

Authorizations

app-id
string
header
required

A unique identifier assigned to each application.

secret-key
string
header
required

A secure token associated with the app-id.

Query Parameters

id
integer

The unique Hello Clever ID associated with the payment request. If provided, this will be used to fetch the payment status.

bsb
string

Bank State Branch (BSB) number associated with the payment request. Required if id is not provided.

account_number
string

Account number associated with the payment request. Required if id is not provided.

Response

Payment request status retrieved successfully.

id
integer

The unique identifier of the payment, used for tracking purposes.

Example:

12345

payee_detail
object

Details of the payee's bank account, including BSB and account number, to facilitate the payment.

name
string

The name of the customer associated with the payment request.

Example:

"Jane Doe"

merchant_name
string

The name of the merchant handling the payment request, allowing identification of the party being paid.

Example:

"Merchant Inc."

gst
boolean

Indicates whether GST (Goods and Services Tax) is applicable to the payment. A value of true indicates GST is included.

Example:

true

amount
string

The amount for the payment, excluding GST. This represents the base transaction value.

Example:

"1000.0"

total
string

The total payment amount, including GST. This is the final amount to be paid by the customer.

Example:

"1100.0"

gst_amount
string

The portion of the total amount that represents GST. This helps break down the tax component.

Example:

"100.0"

expired_at
string<date-time>

The expiration date and time of the payment request, indicating the deadline for making the payment.

Example:

"2024-12-31T23:59:59Z"

external_id
string

A custom identifier used for tracking purposes, such as an invoice or reference number provided by the user.

Example:

"custom-id-12345"

cashback_amount
string

The cashback amount offered as part of the transaction, if applicable.

Example:

"50.0"

pay_by
string<date-time>

The deadline by which the payment must be completed, providing a clear due date.

Example:

"2024-12-30T23:59:59Z"

paid_at
string<date-time>

The date and time when the payment was successfully made, used for record-keeping.

Example:

"2024-12-25T12:34:56Z"

status
enum<string>

The current status of the payment request. Possible values include:

  • pending: Awaiting payment.
  • received: Payment completed.
  • expired: Payment request expired.
  • return_pending: Refund process initiated.
  • return_received: Refund completed.
  • return_expired: Refund request expired.
  • return_rejected: Refund request rejected.
Available options:
pending,
received,
expired,
return_pending,
return_received,
return_expired,
return_rejected
Example:

"received"

description
string

A description associated with the payment request, providing context or additional details about the transaction.

Example:

"Payment for invoice #1234"

refund_information
object

Details of any refund associated with the payment, including bank details and refund amount.

payment_request_notification
object

Details of the merchant's callback settings, including the endpoint URL and authorization information for receiving payment status updates.

nonce
string

A nonce value used to validate the transaction, ensuring that it is unique and preventing replay attacks.

Example:

"unique_nonce_string"

stage
enum<string>

Represents the specific stage in a pending transaction. Default value is null unless the payment amount is incorrect or the nonce is unmatched.

Available options:
overpaid,
underpaid,
unmatched_nonce,
null
Example:

"overpaid"

additional_property
string

A new property added to the BSBAccountObject for extended functionality or specific use cases.

Example:

"Additional value"