The Query Resolution feature in the ANZ Fileactive APIs provides a robust mechanism to handle and resolve queries related to mandates and payment transactions. This functionality is crucial for managing exceptions, disputes, or inquiries that arise during the lifecycle of a mandate or transaction. By using this feature, businesses can ensure smooth and efficient resolution of issues, maintaining the integrity and accuracy of payment processes.


Where query fits in the PayTo process flow:

The diagram below illustrates the steps involved in the PayTo process and highlights where Query play a critical role:

PayTo Bilateral End to End Flow


Capabilities

  • Dispute management: Handle disputes or inquiries regarding specific transactions or mandates, enabling quick and structured resolution.
  • Exception handling: Address exceptions that occur during the mandate or payment lifecycle, such as mismatches or errors in the transaction process.
  • Status updates: Keep track of the resolution status and provide real-time feedback on the progress of each query.
  • Integration with mandate and payment APIs: Seamlessly works with other API features like Mandate Create, Amend, and payment initiation to provide a holistic resolution experience.

Technical requirements

  • Authentication: All query resolution requests require OAuth 2.0 authentication using bearer tokens. Ensure that your application is correctly authenticated before making requests.
  • Endpoints: Use the designated query resolution endpoints provided in the API documentation. These endpoints allow you to submit queries, check statuses, and receive updates.
  • Payload format: Requests should include relevant identifiers and details, such as mandate IDs, transaction references, and specific issues or queries to be resolved.
  • Error handling: Implement robust error handling to manage common issues like invalid requests, unauthorised access, or processing errors.

Key features for developers

  • Flexible query parameters: Customize queries using various parameters to target specific mandates, transactions, or issues.
  • Real-Time feedback: Receive immediate responses on the status of your query, enabling you to take prompt action as needed.
  • Detailed responses: Gain insights into the resolution process with detailed response messages, including resolution status and any required follow-up actions.
  • Security: All interactions are secured with OAuth 2.0 and HTTPS, ensuring that sensitive information is protected throughout the query resolution process.

By integrating the Query Resolution API into your business processes, you can streamline the handling of disputes and inquiries, reducing delays and enhancing the overall customer experience.


General

  • CaseDecisionSchemeRule1:
    • If case_decision is equal to ‘ACPT’, then reject_reason_code and return_transaction_identification should not be provided.
  • CaseDecisionSchemeRule2:
    • If case_decision is equal to ‘FINO’, then reject_reason_code and return_transaction_identification should not be provided.
  • CaseDecisionSchemeRule3:
    • If case_decision is equal to ‘PEND’, then reject_reason_code and return_transaction_identification should not be provided.
  • CaseDecisionSchemeRule4:
    • If case_decision is equal to ‘RJCT’, then reject_reason_code must be provided.
  • RejectReasonSchemeRule1:
    • If reject_reason_code is equal to ‘ARDT’, then return_transaction_identification must be provided.
  • RejectReasonSchemeRule2:
    • If reject_reason_code is equal to ‘CUST’, then return_transaction_identification must not be provided.