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
- fd4d2cef765e8a9405f2dd066e28c0337a4d5ad19f04dd256114cf754223ee2b
- request
- a528899a94fece26c4b69cf3f62f888a8d47e73724caee0de07f89854858131f
- transaction
- 896a8fab1b7da4384a85a13f96f1ecdd3c5bac29f72874a6f9321fa26cfdbb62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12708
the chainentry 12708
- sealed to the entry before
- 7cf3b62a2a6f9952e9506158d86e9b3004ada9dc174e731f97bbc9bdb6f44583
- this leaf
- b0e5ac99eef32482778289deef023d063fd85a0a314c91346be62d0b805c477a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Rrtu0ImdSszZF4WESw+AQqx2BprmkbOWCRj9k5Mk0xAZc3mTgemgvTUQku5XEH9W9wDWeucavr0Ri6TBPEHBDA==