You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STORY: Publish durable payment instruction state events #250
Payment Service publishes durable, versioned payment-instruction state events so downstream workflow components can observe payment progress without synchronous coupling.
Payment Service Maven test and verify, PostgreSQL/Testcontainers outbox coverage, container smoke, and Helm validation passed. The remaining acceptance is post-merge SIT verification of the outbox event in Kafka/AKHQ and PostgreSQL; no provider integration, balance mutation, or redundant CI/test suite was added.
Merged payment-service#13 mainline was built locally as digital-bank-java/payment-service:0.0.2.
Helm lint and rendering passed for the merged chart (0.2.0, app version 0.0.2).
Kafka Helm release revision 4 was upgraded successfully in digital-bank-sit.
The required topics now exist:
payment.instruction.state.v1
payment.instruction.state.v1.dlq
Payment Service release revision 4 completed successfully.
The deployment is 1/1 Ready and the pod is running the freshly built image digest.
Flyway is up to date and startup logs contain no Kafka or outbox errors.
Remaining acceptance is behavioral: create a protected payment instruction, complete or fail it, and compare the PostgreSQL outbox row with the Kafka event in AKHQ. No credentials, tokens, or payment data were recorded.
Payment Service candidate validation recorded: built digital-bank-java/payment-service:sit-outbox-fix-20260907 from PR #14 with 22 tests passing during the container build, deployed it with the existing SIT values, and verified Helm revision 6 with a 1/1 Ready pod. Readiness returned HTTP 200 and structured logs showed a clean startup. PR #14 remains open; functional PENDING/COMPLETED/FAILED state-event and Kafka/outbox acceptance remains after merge.
Candidate built from merged mainline: digital-bank-java/payment-service:sit-payment-events-20260907
Helm release payment-service in digital-bank-sit: revision 7, status deployed.
Deployment: 1/1 ready, zero restarts; readiness returned {"status":"UP"}.
Kafka topics confirmed: payment.instruction.state.v1 and payment.instruction.state.v1.dlq.
Startup logs show the application started on port 8085 with the sit profile.
This records deployment and platform readiness only. Functional creation/terminal-transition, duplicate-publication, PostgreSQL outbox, and AKHQ evidence remain to be executed before closing this story.
An unauthenticated POST /internal/v1/payment-instructions returned 401 with WWW-Authenticate: Bearer and application/problem+json.
No payment instruction or outbox mutation was created by this check.
The remaining positive-path acceptance (PENDING creation, terminal transition, outbox row, Kafka event, and duplicate publication) requires an authorized synthetic payment.internal bearer token. No credential value was read or fabricated.
Governance correction: assigned the native GitHub Issue Type Story. The issue remains correctly parented under EPIC: Payment Rail Architecture (#31) in Sprint 5.
Authenticated payment instruction creation through API Gateway returned 201 Created.
Repeating the same normalized request returned 200 OK with idempotent replay and the original instruction identity.
Completion returned 200 OK; PostgreSQL showed the instruction in COMPLETED state.
PostgreSQL outbox evidence for the instruction contained one PENDING row and one COMPLETED row.
Kafka topic payment.instruction.state.v1 contained matching PENDING and COMPLETED PaymentInstructionStateChanged.v1 events for the same instruction, amount 25 AED, currency AED, and correlation payment-acceptance.
No provider integration, account/ledger mutation, direct downstream call, or secret value was introduced.
Temporary Auth fixture and port-forward were cleaned up; SIT returned to baseline and remained healthy.
The durable payment state-event story acceptance criteria are complete.
Activity
ramioooz commentedon Sep 6, 2026
Implementation is available for review:\n\n- payment-service PR: https://github.com/digital-bank-java/payment-service/pull/13\n- config-repo PR: https://github.com/digital-bank-java/config-repo/pull/48\n- infra-sit PR: https://github.com/digital-bank-java/infra-sit/pull/41\n- contract PR: https://github.com/digital-bank-java/.github/pull/251\n\nVerification: payment-service Maven verify with -DskipUnitTests=true passed with 19 tests using Docker/Testcontainers; the SIT Kafka chart lint/template validation passed. These PRs are coordinated and must be merged before payment-state-event SIT verification.
ramioooz commentedon Sep 6, 2026
Handoff documentation is now prepared in PR #252, alongside the implementation and delivery PRs:
Payment Service Maven test and verify, PostgreSQL/Testcontainers outbox coverage, container smoke, and Helm validation passed. The remaining acceptance is post-merge SIT verification of the outbox event in Kafka/AKHQ and PostgreSQL; no provider integration, balance mutation, or redundant CI/test suite was added.
ramioooz commentedon Sep 6, 2026
Post-merge SIT rollout (2026-09-07)
payment-service#13mainline was built locally asdigital-bank-java/payment-service:0.0.2.0.2.0, app version0.0.2).digital-bank-sit.payment.instruction.state.v1payment.instruction.state.v1.dlq1/1Ready and the pod is running the freshly built image digest.Remaining acceptance is behavioral: create a protected payment instruction, complete or fail it, and compare the PostgreSQL outbox row with the Kafka event in AKHQ. No credentials, tokens, or payment data were recorded.
Related merged changes:
ramioooz commentedon Sep 7, 2026
Payment Service candidate validation recorded: built
digital-bank-java/payment-service:sit-outbox-fix-20260907from PR #14 with 22 tests passing during the container build, deployed it with the existing SIT values, and verified Helm revision 6 with a1/1Ready pod. Readiness returned HTTP 200 and structured logs showed a clean startup. PR #14 remains open; functional PENDING/COMPLETED/FAILED state-event and Kafka/outbox acceptance remains after merge.ramioooz commentedon Sep 7, 2026
Post-merge SIT rollout checkpoint for the durable payment state-event implementation.
digital-bank-java/payment-service:sit-payment-events-20260907payment-serviceindigital-bank-sit: revision 7, statusdeployed.1/1ready, zero restarts; readiness returned{"status":"UP"}.payment.instruction.state.v1andpayment.instruction.state.v1.dlq.sitprofile.This records deployment and platform readiness only. Functional creation/terminal-transition, duplicate-publication, PostgreSQL outbox, and AKHQ evidence remain to be executed before closing this story.
ramioooz commentedon Sep 7, 2026
Additional SIT boundary verification:
POST /internal/v1/payment-instructionsreturned401withWWW-Authenticate: Bearerandapplication/problem+json.The remaining positive-path acceptance (PENDING creation, terminal transition, outbox row, Kafka event, and duplicate publication) requires an authorized synthetic
payment.internalbearer token. No credential value was read or fabricated.ramioooz commentedon Sep 9, 2026
Governance correction: assigned the native GitHub Issue Type
Story. The issue remains correctly parented underEPIC: Payment Rail Architecture(#31) in Sprint 5.ramioooz commentedon Sep 9, 2026
Controlled SIT acceptance (2026-09-10)
201 Created.200 OKwith idempotent replay and the original instruction identity.200 OK; PostgreSQL showed the instruction inCOMPLETEDstate.PENDINGrow and oneCOMPLETEDrow.payment.instruction.state.v1contained matching PENDING and COMPLETEDPaymentInstructionStateChanged.v1events for the same instruction, amount25AED, currencyAED, and correlationpayment-acceptance.The durable payment state-event story acceptance criteria are complete.