Skip to end of banner
Go to start of banner

Feedback Summary v2.0.0-rc1

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Below is a summary of all feedback on v2.0.0-rc1 received from standards users and wider industry engagement.

Feedback collected from Tuesday 12 November 2019 until 10 December 2019.

Contributor

Category

Feedback

Response

Will Maio - Paymark

Payments Initiation API

Addition of refund API links to the Payment initiation V2.0 release candidate:

  • Being able to offer real time refund on transactions initiated by API links is a key requirement for merchants to keep the admin cost down, and for customers to have a streamlined payment experience.

  • For some retailers, not being able to refund means they will have to set the customer up as a “supplier” in the system, resulting in weeks of delay and a huge amount of admin effort.

Refunds are not currently an agreed part of the scope for v2.0:
/wiki/spaces/ACSC/pages/49283242

It should be noted that in the v2.0 standard - Third Parties are be able to initiate a refund to a Customer via these steps:

  • Requesting the DebtorAccountRelease as part of the Customer's original payment-consent (to identify the Customer's bank account details)

  • Agreeing a new payment-consent for the Merchant with the Third Party - to pay the Customer

  • A Merchant's payment-consent may be an enduring-payment-consent - which would mean that under agreed parameters, the Merchant would only need to authorise this refund payment-consent once.

  • Third Party initiating a payment-order with the Merchant's Bank to refund the Customer

Note that the existing v2.0 (and v1.0) standards rely on push payments initiated by the Customer's Bank. If we were to re-utilise the push payments system for refunds - then a refund must be initiated by the Merchant's Bank.

Your feedback on future functionality will be incorporated into the discussions informing the scope for pipeline activities.

  • No labels