Search for transaction data

Transaction data includes payments received from Payment Requests and Payment Initiations as well as payments made out by PayOut. You can access this data as follows:

  1. Navigate to the Transactions view in the navigation bar
  2. You will be presented with a form where you can select from Payment Requests, Payment Initiations or Outbound Payment products
  3. You can specify additional search criteria such as PayID, Client Branch and / or dates to search by.
    1. Not all combinations of criteria are available for all transaction types, when a criteria is unavailable the field will be greyed out. If you need to search on a greyed out criteria try removing other search criteria
  4. Enter the appropriate search parameters and click Search

Payment Requests

Payment Requests search results show PaymentRequest's created in the POST /v1/paymentRequest call


Default search results - payment requests

Here is a description of the columns that you will see by default when landing on this page:

FieldDescription
Client Transaction IDAn ID you provide in the PaymentRequest to reference transaction data in your own systems
PayIDThis is the PayID to which your customer can make their payment to
Client BranchAdditional transaction data point that you optionally choose to add to your PaymentRequests. Examples might include which branch or channel in your business generated the transaction
Created DateThis is the date when the PayID for the payment request was created
StatusThe status of PaymentRequest. May be one of:

- WAITING - the PayID is registered but no acceptable payment has been received
- COMPLETE - an acceptable payment has been received EXPIRED - no acceptable payment was received before the PaymentRequest expired
- RETURN_IN_PROGRESS - a payment was received but is in the midst of being returned to the source account
- RETURN_COMPLETE - the payment was returned to the source account
- RETURN_FAILED - the payment return failed to process
AmountThe requested payment amount

Each PaymentRequest can be expanded to show more details:

These details include:

  • Other parameters supplied in the POST /v1/paymentRequest call such as payment description
  • Data received from the payer such as description, reference and where enabled source account information such as payee name, bsb and account number
  • A timeline of events associated with this PaymentRequest
  • The option to refund the payment back to the source account and information on the amount available to be refunded

Configuring payment request search results.

Search results for payment requests include a button to 'Configure Results'. Use this to specify which columns you want to see displayed in the search results. Any columns selected will be included in the Export feature.


Additional columns to be selected for display in search results are as follows:

FieldDescription
DescriptionDescription of this transaction. It will be the last part of the PayID name that appears in the customer's online banking when they lookup the PayID.
Payment ExpiryTimestamp when the payment request expires and is no longer able to accept payments.
Payment Request IDAn identifier generated by Azupay. Used to reference the object in subsequent operations such as getPaymentRequest and refundPaymentRequest
Parent Payment Request IDThe paymentRequestId of a paymentRequest created with multiPayment set to true and for which this PaymentRequest was created and paid against.
Completed DateTimestamp when the payment was finalized in Azupay systems
Return Created DateTimestamp when refund request was initiated
Return InitiatorAUTOMATIC for returns initiated when a payment to an expired PaymentRequest is received. MANUAL for returns initiated by the refund API or dashboard.
Amount ReceivedThe amount received from the customer
Overpayment AmountWhen the payment request is multiPayment and has a paymentAmount defined, the payer can overpay by mistake in which case the extra amount is refunded back to their account. This value represents the extra amount that was refunded back to the payer. If the payment was for the exact amount, the value of this field is zero. This field will only be present when the payment request is in COMPLETE state.
Failure ReasonIf status is failed or returned, this field will describe the reason for the failure.
Payer Payment DescriptionThe description supplied by the payer when making the payment
ReferenceThe reference supplied by the payer when making the payment
Payer BSBBSB of the payer making payment
Payer Account NumberAccount number of the payer making payment
Legal Account NameLegal account name of the payer making payment
Ultimate Payee NameUsed for specifying the name of the sub merchant for whom you are creating the PaymentRequest for.
NPP Transaction IDThe identifier of the transaction in the NPP network. This is an identifier known by the initiating bank and serves as a unique identifier for the refund.
Settled BySpecifies how this PaymentRequest was completed. Can be one of:
*PayID
*PayTo
*BSBAndAccountNumber

Outbound Payments

Outbound Payments search results show Payments made using the POST /v1/payment call

Default search results - outbound payments

Here is a description of the columns that you will see by default when landing on this page:

Column nameColumn description
Client Payment IDAn ID you provide in the Payment API call to reference transaction data in your own systems
Account/PayIDThe PayID or the BSB/Account Number to which the payment was made
NPP Transaction IDA transaction ID automatically applied by NPP as the payment is processed. It is possible the recipient of your funds will quote this reference number as they may see it on their bank statement.
NameThe name of the Payee this payment is being sent to
DescriptionText you provide in the Payment API call
ReferenceA reference to the payee so that they can easily identify the payer or purpose of the transaction
Created DateTimestamp when the payment was made
StatusThe status of the payment. May be one of:

- CREATED - the payment has been requested but is awaiting settlement
- SETTLED - the payment was settled into the target account
- FAILED - the payment was rejected
- PENDING - the payment is pending settlement
- RETURNED - the payment was initially settled then later returned
AmountThe requested payment amount

Configuring outbound payment search results.

Search results for outbound payments include a button to 'Configure Results'. Use this to specify which columns you want to see displayed in the search results. Any columns selected will be included in the Export feature.


Additional columns to be selected for display in search results are as follows:

Column nameColumn description
Settlement DateTimestamp when the payment was settled. This will only show for payments that have status = 'settled'
Payment IDAn identifier generated by Azupay. Used to reference the object in subsequent operations such as getPayment
Completed DateTimestamp when the payment was processed by Azupay. Only for status different than CREATED
Failure ReasonA reason code for a payment that is in status = FAILED
Returned ReasonA reason code for a payment that is in status = RETURNED
Returned DateTimestamp when the payment was returned. Only if status = RETURNED
Sent via DEThis field is set to true when the payment was sent via the direct entry (DE) network. When true, this payment may take between 3 and 5 business days to settle
Ultimate Payer NameThe name of the ultimate payer. This name is visible to the payee on the payment

Payment Initiations

Payment Initiations search results show PaymentInitiation's created in the POST /v1/paymentInitiation call.

Default search results - payment initiations


Here is a description of the columns that you will see by default when landing on this page:

Column Name Column Description
Payment Initiation ID ID that identifies the payment initiation
Account/PayID Payer's Bank Account or PayID of the payment agreement
Payer Name Payer's name of the payment agreement
Created Date Date when the payment initiation was created
Status Status of payment initiation. May be one of:
  • CREATED - the payment initiation has been created
  • SETTLED - the payment initiation has settled
  • PENDING - the payment initiation is pending
  • FAILED - the payment initiation has failed
  • RETURN_IN_PROGRESS - the payment initiation refund in progress
  • RETURN_FAILED - the payment initiation refund has failed
  • RETURN_COMPLETE - the payment initiation refund completed
Amount Requested payment amount

Configuring payment initiation payment search results

You can configure additional fields to be displayed by clicking the button and selecting the optional fields within the modal then saving. Any columns selected will be included in the Export feature.

Additional columns to be selected for display in search results are as follows:

Column Name Column Description
Payment Agreement ID ID that identifies the payment agreement
Client Transaction ID ID that identifies the transaction created by the merchant system
NPP Transaction ID ID used to reference a payment pulled from a bank account between banks, businesses and payment facilitators such as Azupay
Completed Date Date when the payment initiation was completed
Reference This is used to unambiguously identify the payment initiation
Description Optional remittance information used to unambiguously refer to the payment initiation