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
- fed7f012b4c1bf2b2cf60c916b539c3f06ab2d7fefc235b5aaa5849b2d87eaea
- request
- e745650d56773336a15522d773b429f4c6b7857b89e0fda5b1d12fa96e28f31f
- transaction
- cccf41a3d145469c2851b4a6805675193af172b25b3a552b95ff3ca7e754912ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17674
the chainentry 17674
- sealed to the entry before
- ac53d26fe3a845984778cc73fbac94554885bff91fe0cdf9dbd8e540b5a7f05b
- this leaf
- 17349084d7e856a4785b5dc873338cf24ff0d686896571281e8fb06d311608db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aQLtwZJPUjkUgzPPfQhY27MR5ARAGt5vJwZHiAp1uMHeRNkBeeCs+tozjOtZ2+BfUdmnGrXDzeFtwhCRdXpHDw==