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
- 2f5eef144325a2723dcfb46db76f492350f2a049cc98d5f1bcfcc33c85988d57
- request
- 3a6a7519b27b923694a90fcf01e2660a7ca28caa233730036ae638c84f4bac65
- transaction
- 2eca5b1693488f289f1d3f38bf481cff45d6a59af727466fff77f2e09c78296fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36963
the chainentry 36963
- sealed to the entry before
- 25634a24954574ffd2abfe2b0702206ca41a1ccbf1e50fc99c7eaff772d3cd34
- this leaf
- f5ca10680795885e949a2dcb153eaa54cb4b17a0f4d9385f8d5071c619973158
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aNFPmqlFCVS2PjWe5GwS+KTRcMW/ijqLC4h+S0GZ37OVSzhFYxWELuaptdZ5545Bbk2PlKUJhf1ERqFmIuidBg==