GET
Get Payment Agreement Detail

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
required

The unique Hello Clever payment ID for the payment agreement.

Response

Request processed successfully.

id
integer

A unique identifier for the payment agreement, used for tracking and management.

Example:

12345

payment_agreement_id
string

The unique identifier for the payment agreement, providing a reference to the specific agreement being handled.

Example:

"agreement-12345"

client_transaction_id
string

A unique ID for the transaction as provided by the merchant, used to ensure transactions can be uniquely tracked.

Required string length: 1 - 90
Example:

"client-trans-001"

limit_amount
number

The maximum allowable amount for each payment under this agreement, helping to manage the scope of transactions.

Example:

5000

description
string

A description of the payment agreement, providing context and information for the payer and merchant.

Required string length: 5 - 140
Example:

"Monthly utility bill payment agreement."

external_id
string

A custom identifier assigned to the payment agreement, typically used for tracking and reference purposes.

Maximum string length: 255
Example:

"custom-agreement-id-7890"

status
enum<string>

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

  • created: Agreement has been created but not yet activated.
  • active: Agreement is currently active.
  • suspended: Agreement has been temporarily suspended.
  • cancelled: Agreement has been cancelled.
  • failed: Agreement creation or payment has failed.
Available options:
created,
active,
suspended,
cancelled,
failed
Example:

"active"

created_at
string<date-time>

The timestamp indicating when the payment agreement was created, in UTC.

Example:

"2024-01-01T00:00:00Z"

payment_agreement_type
enum<string>

The type of payment agreement, indicating the nature of the payments involved.

Available options:
MORTGAGE,
UTILITY,
LOAN,
DEPENDANT SUPPORT,
GAMBLING,
RETAIL,
SALARY,
PERSONAL,
GOVERNMENT,
PENSION,
TAX,
OTHER SERVICE
Example:

"UTILITY"

agreement_details
object
payer_details
object

Details about the payer, including either bank account information or PayID details.

payment_agreement_notification
object

Details for the merchant callback, including endpoint URL and authorization header for receiving status updates on the payment agreement.