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
- 9611cd341b534f53524d1acd2a6ece6b08f51edef23bb4848418fb384f8ef06d
- request
- 7a88958ff77ec8ef7ffbd3025028c85b682ce8dec9cc3947ef961fb254d7db9b
- transaction
- 5e73ba1448412146b651487e50c089f8df22edc98244b7c77a642dbd87663587computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 836
the chainentry 836
- sealed to the entry before
- 5a03975d80a17e3536fe19400d8becfa2e6bcf9fbdbe1567b8d03341d414469c
- this leaf
- 3a7eeb1a129bb739cbe057c7173274311ef250735a338de9acaf88fdad12c93e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LGpcWt7LzL0oBoKM9hd3aMW1O/eQNfp1RTO5xjUUG6i4k1zKVHmGfrkxLTPJaNQcw27ojotWgZmuyY3lyXrqDQ==