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
- d0a47ce67f87afefd0ea7ed09a2620f64a4806ac21df796d311bdf0bab391ac4
- request
- 510bc24eaeb84f6fc1332c6c795f3127a7a0e789e76c37f2cd42678e0462ff62
- transaction
- 9bac458f42d94a3454cdfd33869114bbaa9a28dd580c69d188df5812d70e149acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46871
the chainentry 46871
- sealed to the entry before
- 4b276de1293c192cdc22358ac241857e5680c8d127467a06f85375060325dded
- this leaf
- b436525a7d4ba85514dc8e5192351c6a4982f7fe7ddf8ff661077fe1a6d844f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XEl41mj6gDao2Ii3ijFHgaWX5AgZVtXLy0DA80n+01sgKput2ilxniJh+2NfnxVGCum0coIv6LgOmby/dH4DDg==