Ensure Name Request and NameX can accommodate all the new refund statuses

[JohnamLane]

Once new refund feedback statuses are implemented we will want to do the following:

Name Request

• Ensure new statuses don't break existing functionality
• Ensure all receipts presented to clients still work
• Determine if there's a nice way to show all of the refunds statuses to clients while refunds are in progress/complete

NameX

• Ensure new statuses don't break existing functionality
• Determine best means of displaying payment status separately from NR statuses

[seeker25]

@pwei1018 tagging you just so you're aware

We're rigging up the feedback mechanism from BCOL (Should provide us with REFUNDED status for BCOL) Also two new final refund states for PAD and possibly ONLINE_BANKING (CANCELLED / CREDITED)

CANCELLED - The customers account was not charged CREDITED - The customers account was charged, but we've provided a credit on their PAD /ONLINE_BANKING? account

[eve-git]

1. NR sends request to pay-api for refund and updates requests.state_cd='REFUND_REQUESTED'. After the refund complete in pay-api and invoices.invoice_status_code updated to 'REFUNDED', no message is sent back to namex.

2. When retrieving existing NR, UI reads the requests.state_cd from namex and retrieves receipt data from pay-api. UI works good when invoices.invoice_status_code changed.

Question: Does NR status need to be updated in case of 'CANCELLED' refund?

[ozamani9gh]

@eve-git are you actively working on this ticket.... if so, please have a chat with @seeker25 if not, i might give this one to @Madhavkapoor28 he can learn about all the statuses

[pwei1018]

@oanyahuru Please QA this ticket in Name examine application. (need to wait the deployment in Test some time next week) It is similar to https://github.com/bcgov/entity/issues/14252.

[oanyahuru]

@pwei1018 I tested it with various actions, business types and payment types. The messaging looks consistent to me and displays as expected.