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
- 9d5a97c025cc6fddd8a3d1b60baa5418d78901a1ff8f303a84b3da15ceab5875
- request
- 5ab7870a7c9d9d4724a41520b564dec8eea631c7c15f7802682041b728073254
- transaction
- b1f7345ae4b5b3d0cf1ef52c678bc124c61e5df10178a8bc7e401d7e0ca99574computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61873
the chainentry 61873
- sealed to the entry before
- eb12a133523be4e0335aff1891bf3db4feb6539e9874727e98096e7ea30c2859
- this leaf
- 72519bb3716da6b065265cbb7c41405dd3095437724766922e1d4d94888eef26
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YIk0pq1ak/LXRQJxEiUheJ+nBswhXljyKcLTtALjh5KPijEHG3T+49eUZcgnKUB4e1YG+7xifFtLhp+LmgTTAg==