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
- edf77945c318763a038f4ad2901253391042a55175989d4f60a1d729a9032833
- request
- f42ca2d0c2f9705584ae95a85f86f1308aabd0b16196ba61af68f3c442de86a7
- transaction
- c9b36a0683a33ce46e452d735b9dbad18300d5c6cd5ebe501d99dafa61f53f2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41353
the chainentry 41353
- sealed to the entry before
- b7bb3a68724eb8d2e6500a76a9d500b8924690af5567a6210fbf2b62037a08a9
- this leaf
- f46cf8481d9ed2ffbc254bca7a685dc2c8434b36e76c20296ad0e95a77acbc18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y/8C4eX6OsZu46zyHRKs6/pTIcMYHKco5yS2wu3InvuEKxvmOIhAmsKfNm9HzbY0RpcQTpMAH8N1orQAxbAeAQ==