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
- f068b85890b9b51075a734ad059e455c23b6b309a1dfa1c54032ecef53364144
- request
- b4fd786f0d90227a9f66ad8f00030bbe06ff4e8f28d73289820fb279844599a5
- transaction
- a748aef3f7fb65b0f5796cc1944d36e3dc47eac615b40cef3b4d0ddf4c323ee1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60145
the chainentry 60145
- sealed to the entry before
- b912706ed0870e8ec28e89d466ce957b8c9fa056de680abfddb3b0105aa3b7b1
- this leaf
- da34962e2223309d589fa5e28f66e223071a3d6c923a6113952a7776974fdb01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 28H/aDdwFXh+hcIH0DBzbuf5GNOn7CywPBcxZMlY7a/TXZCoQuwFJdy8lQbQPkoobIQUnF4anJVFrh5IGK6dAw==