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
- 20b1510f45d3c9cf30d1e1c7856b687b3ea62d75640cb836eceeb0c10aff6bf4
- request
- dc015dd91cafbd9c3ec1f33bc5585f83d17d95625b61456acc7abc134c870c9a
- transaction
- a6e2bcd3a975fbaac057d2ce03354db56c5c9f210dd111c8e61d91d436a382d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72735
the chainentry 72735
- sealed to the entry before
- 150afc11d84276c26fd79cc8f1d4896fcdde5c52e9cb7cde0d9a4763e4c33813
- this leaf
- 383cbcda00d1e7a0f0fa924b069af0586fb1df322767a7ee2ab54982851c8e65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mOxmK9ALyyKD7OPlpQQ/Xd3oixqydQ4IldZ/L2Yf43Z7vQV3l7dUdK/WJNqbmsF06ei+T7e8HmySBFw1/GQACA==