Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client views refund statuses in their own transaction list #14376

Closed
JohnamLane opened this issue Nov 22, 2022 · 7 comments
Closed

Client views refund statuses in their own transaction list #14376

JohnamLane opened this issue Nov 22, 2022 · 7 comments
Assignees
Labels
Pay Work for Pay Team UX Assurance

Comments

@JohnamLane
Copy link
Collaborator

JohnamLane commented Nov 22, 2022

Assumptions

  • This will be an enhancement of the existing account-level transaction list
  • For refunds, some payment methods (PAD, BCOL) do not currently have status feedback necessary to support this feature.
  • This work will proceed prior to implementing a refund UI, and will not contain the intermediate statuses needed to support request/approval flow.

Scenario 1
GIVEN I am a client
AND an ops dev has started my refund
WHEN I view the payment in my transaction list
THEN I see the payment status of REFUND REQUESTED
AND it is indicated when the refund process started

Scenario 2
GIVEN I am a client
AND the back-end process for my refund has finished successfully
WHEN I view the payment in my transaction list
THEN I see the payment status of REFUND COMPLETED

Scenario 3
GIVEN I am a client
AND I have paid for the same item multiple times due to a defect
WHEN I view the payment in my transaction list
THEN ??? How to show this hierarchy of Invoices and Receipts

To be investigated:

  • how does each draft payment look across each payment method?
  • Confirm what scenario 3 above looks like.
  • Review how to nest NSF charges under the original payment

Existing Columns

  • Transaction
  • Folio Number
  • Initiated by
  • Date (Pacific Time)
  • Total Amount
  • Status (with info icon)

New Columns to be added

  • Transaction ID
  • Payment Method

Definition of each payment status:
Existing payment status:
COMPLETED - Funds received
PENDING - Transaction is pending
CANCELLED - Transaction is cancelled

New status to be added:
APPROVED - Transaction has been approved, awaiting processing
REFUND_REQUESTED - A transaction refund has been requested
REFUNDED - Transaction has been refunded
SETTLEMENT_SCHEDULED (for NSF) - Settlement has been scheduled for NSF

For REFUND_REQUESTED (Has requested a refund, but hasn't been refunded - Note PAD and BCOL have no mechanism to set this to REFUNDED, DIRECT_PAY has the ability to make it to REFUNDED)

status info has been extracted from #14048

@kialj876
Copy link
Collaborator

currently in dev

@ethantspitt
Copy link
Collaborator

Observation:

  1. For PPR search, there's no payment status displayed
    1.PNG

  2. the payment status help text has been updated in UX Pin
    image.png
    @JohnamLane @janisrogers do we need SBC finance to take a look if the copy above make sense?

@kialj876
Copy link
Collaborator

kialj876 commented Jan 27, 2023

Hey Ethan I think the payment status not showing for PPR search is a data issue with dev. Any new ones show up fine right? I will do some verification that this wont happen in prod

--- I have confirmed that this is a data issue in DEV only

@ethantspitt
Copy link
Collaborator

  • Updated wording in UXPin
    image.png

  • transaction types should show details like previously to be more clear to the user.

@kialj876
Copy link
Collaborator

kialj876 commented Feb 2, 2023

@ethantspitt these changes are in dev now

@ethantspitt
Copy link
Collaborator

Thanks for the changes @kialj876
Verified in Dev, ready for QA

@kialj876
Copy link
Collaborator

kialj876 commented Feb 3, 2023

Deployment notes:

  • dependent on auth-web and pay-api
  • before deploying the pay-api into PROD we need to update all invoices.details='null' to be '[]' (already done in dev/test) Done
    • check nothing is still updating it to 'null' still being updated to 'null' travis fixed
    • data fix for 'null' needs to be run in TEST/PROD again after deploy
      • test
      • prod

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Pay Work for Pay Team UX Assurance
Projects
None yet
Development

No branches or pull requests

4 participants