POST
Create BSB/Account Number Payment

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

The full name of the customer for whom the payment is being created.

Pattern: ^(?![! ](?![!]*$))[a-zA-Z0-9 ]*(?![ ])$
Example:

"Jane Doe"

gst
boolean
required

Indicates whether Goods and Services Tax (GST) applies to the payment (for Australian merchants).

Example:

true

amount
number
required

The total amount to be charged, specified in Australian Dollars (AUD).

Example:

1000

description
string
required

A brief description of the purpose of the payment.

Pattern: ^(?![! ](?![!]*$))[a-zA-Z0-9 _-]*(?![ ])$
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

Callback configuration for receiving payment status updates.

expired_at
string<date-time>

Expiration date and time of the payment, in UTC. Must be at least 15 minutes from the current time.

Example:

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

external_id
string

A custom identifier provided by the merchant for tracking purposes.

Example:

"custom-id-12345"

Callbacks

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

Body

application/json
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"

Response

Callback received successfully.

Response

Payment request created 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"