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
- c2a0032246939c72c5f02ce11ae0afe4c9a989d63efc30277dd8443e17474a68
- request
- bda2cb838ae8a9092333cc8040ca7a42546c402d3c033e2431417628ae4e08a8
- transaction
- cd234d20bbba64f664457fe77263a8d7449a8f61e073406240023f8bff705a8dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42740
the chainentry 42740
- sealed to the entry before
- 0d618c558c09a8fd48834d45a57dc66dbd5eeab2f370c2147854ae3562e7a0d7
- this leaf
- 3093d9ec00b016a62297e57ab64bac7425b74aab2324a25edd7cc05f0c350073
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wyCgva/3f9yPzFfQBbjniJdGuX480zv55MyHz/feMxzV2n8o0RsHtPrDW4MzlnpTZE4WVjIPcZWd3CwnldSaCw==