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
- 11c5f5498fe7ac867b6514f77c9582eed274dcede1dd4c81f09a219977bd3d2a
- request
- 1ba179ca614ef880a062888cfa6ba692c93c94a88bf920e1d0de138cbc5e8553
- transaction
- 93e4fbcae2d8ab9fcf893a845993df9522c8a4977f0c41a2748191f7084d9f40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28360
the chainentry 28360
- sealed to the entry before
- 719edf3cd07c8bdfdf5860f6e8bf00e70ad87b24882df255d09dadd2c2c8e41a
- this leaf
- d639516663d6b28132fbc14aeafc613e4f849dd66385141dcd4f2434dfeccaec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Jr2aq5II1ET1jZOE0jUyF30xwCgVmMJvDk9frK6z3UuPcKPL/nzUb9+g5Az5Pr0tIXkIwsaAMctrGhJQ7oXUBg==