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
- 11c02eb9814fed5716ea1c256f297140731222ebfbcba2305addcdca8d7c3f4d
- request
- df0964337023b7f03cc2d468774864ede01d958ef0c5198cb36e41fe69f8852f
- transaction
- 25e95677ac41aee9cc061462ebdf3ba08d98cd69474cd5abc7044d78bc5db4a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29289
the chainentry 29289
- sealed to the entry before
- 66154eba72a66ea9f9ea663aa7b6f4d529fc0cc79f9f55e8dc6f25a7e0ce93bd
- this leaf
- d927122e8bf553be85de2d73a586f1bebf324e4f18d4628be53380788652c89c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ERj7mYbh/15J2KYxmO7wVx4I9e5WL7jN8xz+tqnMWaJn+VqMNuaoyCydiGeqBQ2NwaTPkMBFEhXdJtbuPFFNCA==