why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 7ef224054aa9b01ffbc9bf0afaff52dc5629152dc9766af25e462a852f75f8eb
- request
- eba92a6a5d964a43fa80ca14388cf619a122a61e3dce0852440b2a335ff377c8
- transaction
- f58f2a4a448ec846e5950ce4b8bead6d3a7d580a56ddf34fd08d07f80e354b91computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25629
the chainentry 25629
- sealed to the entry before
- 7fd046f7c771a4ac3c7ff9c4c00d50342c9bea83775fe75d906ce5a922fda671
- this leaf
- 42f955a8e8cd05d38883bf1c92858860213c7ba301da8542ed30a36cde14daa5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EkHJ0sGGqTDU+lR25STM4vxh3rntEOsOmCPpAG+tmlxHbeA0UUVRzPQhKUkI185bdW1ob6raqNhXe4g62WLDAQ==