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
- 649d54f77b30158d7527afe79235473dbb2fd9ece2da22c4132258d53c82a703
- request
- a534cf357880f2f7c678ecdf39fb13402c41934adcc404d4c98b4d96c685d1f5
- transaction
- afb0fdc91a0ab545cf934ebd81f36de93d68bb9add7e1f6b13df55496f365a41computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 626
the chainentry 626
- sealed to the entry before
- 37e94d32f0e3a9a407b690c41d7a4166da0c7518ae2c8d115f84922c7125ab9a
- this leaf
- b725f53e5075c3c5206cdcde99d3f2cd7d001301d33f8d90b122ddb792adf113
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GZZDGmjczGWHUCtc9pG1rcBs9dH9ovpmgJnqeprf+s91TAEwzoGO2PoUHUZeuRMP6EOdNjFicKRbZcoT7bzuCA==