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
- 3e5bc254b06a2ca18553606758f4aa8f715089acc63488f2a5284fedd7b6516d
- request
- 43af29ff995a70ac0f4919e1048861cd5994c49830f0483a0ade88446113a170
- transaction
- 10a3dd0fa6971bff4facfc68cb72fb6a1b3ff18cd63c11902825510bf2a4e1a4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68058
the chainentry 68058
- sealed to the entry before
- 1ffded8a0a79f59076ef2d2bf98b8147f23c8bc0a59b0ef7aefe5933672f8fbe
- this leaf
- e3ee9874c5a808305f30e596609afb7de8a4a2edc04bbb20e9f6d88d42528a90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wZsxyUonIZJzEU6Hq3dRWaM8NbrzFoUK8MFHPOXZvfUtwfo92j4BaJPwWobG5Fy6heUhH3NmQ8LJO56t0ukQAQ==