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

SPIKE: Refunds #25545

Open
mbertucci opened this issue Jan 28, 2025 · 0 comments
Open

SPIKE: Refunds #25545

mbertucci opened this issue Jan 28, 2025 · 0 comments
Assignees
Labels

Comments

@mbertucci
Copy link
Collaborator

From John Lane

Please see line 9 of this doc. Apologies as the link above is for a personal version. https://docs.google.com/spreadsheets/d/1Mex2kMDvVoPo8hy4l9De6C888ceXKokSJH-mHRbB2ZA/edit?gid=0#gid=0

For this manual ops flow, the lab ops team will execute the actual refund API call. The Pay DB will track the refund status, and it will be accurate throughout the back end (CAS), but STRR app will need to update their record. e.g. it may show PAID in STRR unless the refund status is pulled from Pay API and updated in STRR

so no need for STRR to have their own refund interface - they can just go through IT OPS? Ok.
From Travis: What about regulations related to refunding the SBC Connect service fee?

From John
I've got to catch up on this part.

From Mihai
Since the Service fee is charged as a fee to recover the capital cost of using equipment and installations to perform a transaction, a case could be made that, if a transaction was completed, the Service Fee should be non-refundable, should we decide to refund the cost for that transaction. It is my recollection that in 2020, when we first implemented Benefit companies in Modernization, an executive decision was made to include the $1.50 Service Fee in the refunds, and not hold it back. Something that could confirmed, and re-visited as needed.

John
For today, we refund both the stat and the service fee. Is there another question that needs addressing?

@mbertucci mbertucci added the STR label Jan 28, 2025
@mbertucci mbertucci self-assigned this Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant