Spike : Solution for calling back the client/partner services on payment events

bcgov / entity

ServiceBC Registry Team working on Legal Entities

Apache License 2.0

23 stars 58 forks source link

Spike : Solution for calling back the client/partner services on payment events #5917

Open sumesh-aot opened 3 years ago

sumesh-aot commented 3 years ago

Description:

During our meeting with Court Services Online, they put forward the requirement to propagate any payment events as a callback. This would be needed for many of our partners. This ticket is to do necessary research and for a PoC.

FYI : @lmullane

Acceptance for a Task:

[ ] Requires deployments
[ ] Add/ maintain selectors for QA purposes
[ ] Test coverage acceptable
[ ] Linters passed
[ ] Peer Reviewed
[ ] PR Accepted
[ ] Production burn in completed

sumesh-aot commented 3 years ago

@thorwolpert Assigning this to you as per our discussion. This is not an immediate priority, just wanted to get this ticket created before I forget.

thorwolpert commented 3 years ago

@sumesh-aot got it, can it go into the next sprint starting next Wed?

sumesh-aot commented 3 years ago

@thorwolpert Sure, if you have bandwidth for next sprint. Thanks.

seeker25 commented 1 year ago

I don't think this was done? A service account was provided that allows CSO to look up their invoices.

mstanton1 commented 9 months ago

@JohnamLane should assets be tagged in this? Would there be an impact for Assets if this was investigated?

thorwolpert commented 9 months ago

This was prioritized out back then. We were following the OAS3 callback approach, leveraging pubsub behind the service, fairly close to how we are doing the callbacks for large reports in PPR already.