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
- de5347beea9ef1cdc939eaee796f601070eb1dc3676d9945bccf7a841fc4f728
- request
- 6e510c39db8e4268315c4111c8ab594b6bbbe857586704a9caef7dfc0865a5d4
- transaction
- 941b448332db67bab928e6c0eb6848cc511739e02e2a96ce924622ec9df921c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68981
the chainentry 68981
- sealed to the entry before
- 2cb58519e47f47c6956ef51c09df11f54d6fc3ee22d89eeba36dfeafc953c83d
- this leaf
- dd648cb511e950a37cd89a084fd8bad964bdfb832840fe4631c2caaa907d60d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1gufRE01pPvzqqooCmQZfvDvQgBxUeZL3fmShJGj8db0TQQbF4vd+t4uEa/tl5StqI7RP7Eubt08pl21pRySCw==