feat: payment status#127
Merged
Merged
Conversation
Signed-off-by: Berend Sliedrecht <berend@animo.id>
TimoGlastra
reviewed
Jun 15, 2026
TimoGlastra
reviewed
Jun 15, 2026
TimoGlastra
reviewed
Jun 15, 2026
Signed-off-by: Berend Sliedrecht <berend@animo.id>
Signed-off-by: Berend Sliedrecht <berend@animo.id>
TimoGlastra
reviewed
Jun 17, 2026
TimoGlastra
approved these changes
Jun 17, 2026
Signed-off-by: Berend Sliedrecht <berend@animo.id>
Signed-off-by: Berend Sliedrecht <berend@animo.id>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements the payment transaction status polling
flow from the EUDI Payment Status spec. After a
Wero SCA credential is issued, the wallet can poll
transaction_status_urlto get the status code.credential_metadata injection is done via an
Express middleware that patches res.send in
front of the OID4VCI routes, since Credo has no
hook for credential_metadata yet that I could find.
Generic records are used instead of a real payment
backend because the playground is self-contained.
wero-credential-token-{jti} links a credential to
its transaction_status_token without it appearing
in the credential or presentation.
transaction-status-{paymentTransactionId} holds the
current status, starting at PDNG and updated after
the SCA presentation is verified. The token is a
random UUID rather than a signed JWT, and status
transitions are triggered locally by the verifier
callback rather than by an upstream payment event.