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
- ef76c823611e18c095c5178a5a09ecda586665726d12e335b68344ba9a1aa6e9
- request
- a8dd2e7eb1e120f852850e5171e310496ee5031fe432948ba96d6f9ec4639043
- transaction
- b7d77db0d7f05f1e29f94ba64f73e5ff2415c5ce09a83db69563fafbfffb0c39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73363
the chainentry 73363
- sealed to the entry before
- 0ce9074a0f44bf3278ef0eec097e23b664d78ab14164389bd40298bb50559d27
- this leaf
- 4579090f97eceb50aa5824639beb5853b69bc7d45b9782d016e70fad4f198431
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BcavG1n8WdTP/0mzO6Q+0Wd75H+uXiU8t2UMnR19Z8EMlY0Iw9FKbSrPxTwxe72YinMyR3OpHZJQg8JWN3wQBA==