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
- 403d8d23bb2e4e6f4c0ea31830da9d6f05d503ccb25aa6eeedead7285323adde
- request
- 22d190f3f9bad22308810572eaf6467d6c5cb3394be4af6012b046401ecd717a
- transaction
- 79304b471b316fae48188c4d2b46ea0c1229b5feeef09e02e231bb0b5adee307computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21433
the chainentry 21433
- sealed to the entry before
- 85b83a2f2b4b7a3f80ef725cf886b22a2b0f564388e413fefb3110ea6b5647ea
- this leaf
- 51b9a3af4f98fab462bb614a476168c932f5d50c173bd7e416f50a85455a6d30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S/TvGLdjL1qkPSsl/Fp+KOkBpelOmGgQlvoNtKMSyaHyOhVuX+BdWDQlx1V0dq+Ss6Lgq/t/O1Gm3UHLzg9VBw==