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
- 5224826d572fc2739dc34bfc191c35307e464a7907716506490228f36460e40a
- request
- e5f6e4941e4d7680d56deaab64932127a7b64fc73855f30c892d022ce17c3c77
- transaction
- 017037f96ddb05c61d492f64185059dc13a1a79382a6cea47c97855344df8555computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69834
the chainentry 69834
- sealed to the entry before
- cc13134c8f531075f421616fcc7acf19ac841dc38b0992f351f55cc98df45c9a
- this leaf
- 12ecd4d193c57221ecc6149104ad79375159c1d19cdafab4b7dc69c86a0b48c1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G53sPepFWJ/BZQWNuIyUg3vWnM6HS98pxVfk4zBAFU/iLH47yyJUamhguCUNOpGQBpVr0S9oEYuV0tqw00bNBQ==