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
- 721d45cb32f337164f2bafe053ec32a1f7fb527a95018cef81dfedab88a383ea
- request
- 920e3416f1ef57c0a2f887b6d6a8042d4572d9a9dcb4dfff6b64707445a81b47
- transaction
- c73bb0b7b428a383514b3883e5690cafe660f47096ff5a4a5a11efed2b713b84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65869
the chainentry 65869
- sealed to the entry before
- 55852a31511b405b30f6dedb49d0a2703dd7529b2d760f6d6fbb069a597454f6
- this leaf
- 56069cc0c7410caf1450f16fe89a3ac74c28caf1d65ce83aa14a30550a76a6a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pIEJv2KZ5c84tMEQgwBQKSY9HmMQxbGg03BZLgFthfZU+ARHYRbVudqz9qxOH2cPYMMAQ3vPlS75gCLNNjhaAA==