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
- 0c5a14aede86790f9bee22780453c402828f22be827958d09bf4f9d81c4a805a
- request
- 93234eb8bf00a5022a800ccca74aad79876929fafe3737df544106509c0eb53e
- transaction
- d2862889e027a8425b439fe7df0402e1b6cbce7adce51486d225f19e9faefb7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55286
the chainentry 55286
- sealed to the entry before
- 08c0477daa5dcf345ad1aaa446a2a144614860b04ec96e10ba211abfc5da0e24
- this leaf
- 2b2ef01ff4e96d11510708b8b14ea0ff33db45e26586d74b4ff9ac06b7db2e3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2K50gEN/XGcQuySbTiry6a0GcgJ3NLeYdbyweBKdO4jamwD96hoLmqOTx4L1uaNGvxZQchRCqvuYUZoBKI/rDg==