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
- d161cc7d8c7b120255627fb134190c7f5051287143c3f2abe927b13345d1e8d5
- request
- 49f6a11c07ae270379959ed7ed72ddc0ba2b3613ccb6c39ba48785ccb2c33fd8
- transaction
- b496b36ff5e0fc796e04ae04a21980a7bc3cddcccad72827547a039da1879697computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63133
the chainentry 63133
- sealed to the entry before
- 8735361f1967584bd9f68763541c93fc1cc4a4928366b5323aa2d085cd9339f0
- this leaf
- c2c61fc14e9c19f316bf6c700f7a45906ea5569012800207a1b082f8e35fe5a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V9eWReWXnkMdxNPcC08AJu7I4LDX1DhWW+9dvrTNMimaH1D2ENr90fZYOVjrjQ1bnKMoNsUA8LnWR6shWNunAw==