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
- 83ad58121aaf5cc4a7a3deae727571dbda3c4bdcb147e2d2b104530cc75f8e9f
- request
- 31d68b686cfc3fff51fb19cac999b8d1f41dedcc5e57324497d3fd89a11ea0ee
- transaction
- 2e77e787850bfe8751d8de20d624a352cd662f0e8ba18a8c1e3728ff93df50bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2010
the chainentry 2010
- sealed to the entry before
- 00ece150a34e2f12f30dd6252ac19e8f0b3e174816e689a8256511f53b7e8bf6
- this leaf
- 99ebf274a53e785a7b00703bb5cfb8725190d9f06d61b3466025652477d7cd7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Dv5cGtunRAC1p73mdAlyy37bbEJUz8ahJcCiZqdmKnM3qakTxjMrB1+RCNhc7AsbxvRbdcOfwv6sTjIM6uVqDQ==