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
- 1500ca89f0f2e410aa3c32e23e529bb142a273b5af1d7dc48d62ccb6699b96ff
- request
- 62b6ac20b6fa05cc37b3272ef3d225ef994a4df94dbe484b5c9c8961b515d8c0
- transaction
- a017dcffc200fb3cbe60ebb462511ffe7b950d4dded30b269eb64fa21bf1da72computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65953
the chainentry 65953
- sealed to the entry before
- 01f1d8d4d83f7c3972c2205f0a14af3ff44de58b89e279311885ac5c7ae09d36
- this leaf
- a3506aaaa164739d95a9761165fc7f34c519253559fe71a63ad67e137703b6f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SJf6eJd8DKUmzzMRNsQBYNCiNVSIeY2buBBjribXYaGDJ2D5tKlwHH12be4iEW76nCEw+6sDrqwbtD0ceUnJDQ==