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
- 9a3f8b0b1eaca1723e6ba3720802563b4013c5b4f0a097d64744e13131bd21e8
- request
- 67c27f0ce523de724a6f3388c1cbf98a155940f753cc38354645fa91c455150b
- transaction
- 0fdb8cff7838e18df019f60313dcecf0ad8c5951565b66047b1c51384ad088fecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64702
the chainentry 64702
- sealed to the entry before
- 932840e15df45ea693c67aa1acdfde60c192a35301f85ca6d2c8c984bbb8e731
- this leaf
- 01017824aff9537a6827d575a3cc902439077331b164e9c53e4340e3141106ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ewaawYZyvFJUGX/QO0fPf21egBG5j1rGhszz7TDS+NfbPjuskAv/rp1cuPN8vRm9J2vtq2ll4riS3vZniD36AQ==