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
- aa128a087bcc2c46ac42c1bb84cca40234e2c0cc95c580ef4913b98bd92ec76c
- request
- aa4930d1215def9366f488596c0e35cc6dfafdd95456ce887e7f3de72e49b5d6
- transaction
- 80e0faaed0b5b68f386a5c4c12586fdf099959ccbd4cd3fdd4279c7363e5eab9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71
the chainentry 71
- sealed to the entry before
- 5e5e1793088910ce04586eb968c5872c827936f2f5096c2e121063827d9b0c32
- this leaf
- 7a2d9a37f2d3f042ecfd019007d43230f8dd705f637bbe3f609d27ab05245f4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TDnH1vFgdhRzXKmFixdeePF7rRGrXaZfOmy12+t7Uha/ruebRC7vv20S2Ot2KbkbFjiAW6vG8/61k7XvecBjAw==