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
- dd533b8614c3277d01c757c7ba1dc77a73156cc66a30a52f3fd5ff907ec1fb5a
- request
- 33f2ad3860bcad229c8fc7c36a94186582017ef90bbe470e4da7eb965cf6dbb1
- transaction
- f71abbdba49113e069435959f08e88a81ad5c82d041ed56cfd848957aff98ef7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2978
the chainentry 2978
- sealed to the entry before
- dadc9ef530d3b1c6a592073cc3ac21406d09bd9e2201f1386d33b380a9a84938
- this leaf
- fab53c0f7a0167a28d0f6ef9683266fcbcc099b0703c57b263eac43f656eb430
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8CfJELtyeOdE7702Apz60oraW0xXLfbkw37EriOjHbMsYDv79IzgcD0hP68RRuVDSXhNEI2qNGCi59PnushVCA==