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
- 2dbc0e52a8f5ad25ef85e230d611091b8f03b29c526d6cd0b6275415e2143d3a
- request
- 16318b12657da35701d475391f6138483cc3dee8a3ef7c1cf773fe693f3dc626
- transaction
- 5e0a2c6e3732439ab031da7a69e9b9c4bdd6dfade6f01fb6194af492aab4a260computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21764
the chainentry 21764
- sealed to the entry before
- 69e11f60a767911146943e169ed60c32bbd8894b671847bea54f906e747f3a3c
- this leaf
- 5eb9b07afb331e714b23db269b9c49152059920ccf9bdf8f2c0af00c6909068a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HID0wv9Q6wmsga/l7KQIZ5PLBKkO5QlbHiCzclz2tDJKKHvP9GDGTjM3Ib04Vy75PxCkf/htVJyghSQ21lxXAw==