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
- 9abd91596d9cf7d4f0239032b26b00260f1265e2ab2f528a159d06cda09767de
- request
- 302950c38179ee265477ad4c01a7bcfe8819daef401d538260f4d35d6ee4d210
- transaction
- c19de877ae626876c88b11c239535d4a424e82a39355eb51b4b5544a0dc8a2abcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65428
the chainentry 65428
- sealed to the entry before
- 6d3f21aa85d18c15ad9654d453707fb7b04ff673f14be655b929fbf9a68fc7cd
- this leaf
- 7043131c019d25ee8dd6e08a878eef3892b066ae5f20081b81816713358461df
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yl0NHZPwkiVKvfg/Z/xpyRCWtS7L2JjahA1evAD75MUgVPjHdYdlbaGmZNoXOE9p6G8Fb6dKYBcaDKDM9f4GDA==