POST
Create One-Time PayID

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.

Body

application/json
name
string
required

Customer's full name.

Example:

"John Doe"

gst
boolean
required

Indicates if Goods and Services Tax (GST) applies for Australian merchants.

Example:

true

amount
number
required

The total payment amount for the transaction in AUD.

Example:

100

description
string
required

Brief description of the payment purpose.

Example:

"Payment for invoice #1234"

emails
string
required

Comma-separated list of email addresses for notifications. Only lowercase letters are allowed.

Pattern: ^([a-z0-9_\-\.]+)@([a-z]+)\.([a-z]+)(,[a-z0-9_\-\.]+@[a-z]+\.([a-z]+))*$
Example:

"customer@example.com"

payment_request_notification
object
required

Details for merchant callback notifications when the payment status changes.

prefix_static_payid
string
deprecated

Static prefix for the PayID, used to generate a PayID in the format prefix_static_payid@example.co.

Pattern: ^(?=[a-z0-9]{3,35}$)[a-z0-9]*$
Example:

"abc"

expired_at
string<date-time>

Expiration time of the PayID in UTC format. Should be at least 15 minutes from the current time.

Example:

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

external_id
string

Custom identifier for tracking purposes, set by the merchant.

Example:

"custom-id-12345"

Callbacks

POST
{$request.body#/payment_request_notification.endpoint_url}statusChange

Body

application/json
id
integer

A unique identifier assigned to the payment request, used for tracking and referencing purposes within the system.

Example:

123456

balance_id
string

The identifier of the balance associated with this payment request, allowing for account management and tracking of specific transactions.

Example:

"HDCHJSS"

name
string

The name of the individual or entity associated with the payment request. This helps identify the payer or payee involved.

Example:

"John Doe"

request_payid
string

The PayID generated for the payment request, used to uniquely identify and route the payment to the correct recipient.

Example:

"payid123@example.com"

merchant_name
string

The name of the merchant managing or handling the payment. This field is useful for recognising the party to whom the payment is being made.

Example:

"Merchant Co."

gst
boolean

Indicates whether Goods and Services Tax (GST) applies to the transaction. A value of true means GST is included.

Example:

true

amount
string

The amount requested for the payment, excluding any applicable taxes. This field represents the base value of the transaction.

Example:

"100.0"

total
string

The total amount due, including all applicable taxes such as GST. This is the final amount the payer needs to pay.

Example:

"110.0"

gst_amount
string

The portion of the total amount that is attributable to GST. This helps in breaking down the tax components of the payment.

Example:

"10.0"

expired_at
string<date-time>

The expiration date and time of the PayID, indicating until when the PayID is valid for making the payment.

Example:

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

external_id
string

A custom identifier provided for tracking purposes, such as an internal reference or an invoice number.

Example:

"custom-id-12345"

cashback_amount
string

The cashback amount, if applicable, that the payer is eligible to receive as part of the transaction.

Example:

"5.0"

pay_by
string<date-time>

The last date by which the payment must be made. This provides a clear deadline for the payer.

Example:

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

paid_at
string<date-time>

The date and time when the payment was successfully completed. This is used for record-keeping and verification.

Example:

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

status
enum<string>

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

  • pending: The payment request is still open and awaiting payment.
  • received: The payment has been received.
  • expired: The payment request has expired.
  • return_pending: A return of funds is in process.
  • return_received: Returned funds have been received.
  • return_expired: The return process has expired.
  • return_rejected: The return request was rejected.
Available options:
pending,
received,
expired,
return_pending,
return_received,
return_expired,
return_rejected
Example:

"pending"

description
string

A description accompanying the payment request, providing additional information such as the purpose of the payment or related invoice details.

Example:

"Payment for invoice #1234"

nonce
string

A unique value used to validate the transaction, preventing replay attacks and ensuring the integrity of the payment request.

Example:

"unique_nonce_string"

stage
enum<string>

Represents the specific stage within the pending status. This value is null unless the transaction is flagged for being overpaid, underpaid, or having an unmatched nonce.

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

"overpaid"

refund_information
object

Details about any refunds that are associated with this payment. This includes information about the refund PayID, refund amount, and any reasons provided.

sender_details
object

Information about the sender of the payment, including reference details, bank information, and account holder's name.

short_invoice_url
string<uri>
deprecated

A shortened version of the invoice URL for convenience. This can be used to quickly share or access the invoice details. Note: this field is deprecated.

Example:

"https://short.example.com/invoice/123456"

invoice_url
string<uri>
deprecated

The full URL of the invoice related to the payment request. This provides access to the detailed invoice online. Note: this field is deprecated.

Example:

"https://example.com/invoice/123456"

Response

Callback received successfully.

Response

Payment request created successfully.

id
integer

A unique identifier assigned to the payment request, used for tracking and referencing purposes within the system.

Example:

123456

balance_id
string

The identifier of the balance associated with this payment request, allowing for account management and tracking of specific transactions.

Example:

"HDCHJSS"

name
string

The name of the individual or entity associated with the payment request. This helps identify the payer or payee involved.

Example:

"John Doe"

request_payid
string

The PayID generated for the payment request, used to uniquely identify and route the payment to the correct recipient.

Example:

"payid123@example.com"

merchant_name
string

The name of the merchant managing or handling the payment. This field is useful for recognising the party to whom the payment is being made.

Example:

"Merchant Co."

gst
boolean

Indicates whether Goods and Services Tax (GST) applies to the transaction. A value of true means GST is included.

Example:

true

amount
string

The amount requested for the payment, excluding any applicable taxes. This field represents the base value of the transaction.

Example:

"100.0"

total
string

The total amount due, including all applicable taxes such as GST. This is the final amount the payer needs to pay.

Example:

"110.0"

gst_amount
string

The portion of the total amount that is attributable to GST. This helps in breaking down the tax components of the payment.

Example:

"10.0"

expired_at
string<date-time>

The expiration date and time of the PayID, indicating until when the PayID is valid for making the payment.

Example:

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

external_id
string

A custom identifier provided for tracking purposes, such as an internal reference or an invoice number.

Example:

"custom-id-12345"

cashback_amount
string

The cashback amount, if applicable, that the payer is eligible to receive as part of the transaction.

Example:

"5.0"

pay_by
string<date-time>

The last date by which the payment must be made. This provides a clear deadline for the payer.

Example:

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

paid_at
string<date-time>

The date and time when the payment was successfully completed. This is used for record-keeping and verification.

Example:

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

status
enum<string>

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

  • pending: The payment request is still open and awaiting payment.
  • received: The payment has been received.
  • expired: The payment request has expired.
  • return_pending: A return of funds is in process.
  • return_received: Returned funds have been received.
  • return_expired: The return process has expired.
  • return_rejected: The return request was rejected.
Available options:
pending,
received,
expired,
return_pending,
return_received,
return_expired,
return_rejected
Example:

"pending"

description
string

A description accompanying the payment request, providing additional information such as the purpose of the payment or related invoice details.

Example:

"Payment for invoice #1234"

nonce
string

A unique value used to validate the transaction, preventing replay attacks and ensuring the integrity of the payment request.

Example:

"unique_nonce_string"

stage
enum<string>

Represents the specific stage within the pending status. This value is null unless the transaction is flagged for being overpaid, underpaid, or having an unmatched nonce.

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

"overpaid"

refund_information
object

Details about any refunds that are associated with this payment. This includes information about the refund PayID, refund amount, and any reasons provided.

sender_details
object

Information about the sender of the payment, including reference details, bank information, and account holder's name.

short_invoice_url
string<uri>
deprecated

A shortened version of the invoice URL for convenience. This can be used to quickly share or access the invoice details. Note: this field is deprecated.

Example:

"https://short.example.com/invoice/123456"

invoice_url
string<uri>
deprecated

The full URL of the invoice related to the payment request. This provides access to the detailed invoice online. Note: this field is deprecated.

Example:

"https://example.com/invoice/123456"