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
- 2049a1bc568a4b89ef822c8f4c4f2e04e9e4f87c712eb73ef6104dab98d50e61
- request
- 7538310ec849ce0bfad1a3377f88ee45e43643d6b162385cc889a8c2ccb83102
- transaction
- 3d296911a16962965a61573f43fd5181e63fbee206e014271d20d07c7ed86b27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1760
the chainentry 1760
- sealed to the entry before
- 2af84a7f9938525b429a3db23f3973a841a6a8c8756ed37e3d1dde0311fd003e
- this leaf
- a14f331cb602b5cb31d06221c8d75993ee88386fef932db334549ba7d22944d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +aVOyGAuEmU7JoDkM2Mhl9HlGG+B0FDqhg9OilcfQSZSAMtukoe6onoXtxpBP3yaBbWz50oRizdvKslCwkMhAw==