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
- 07fb11afa704a938f3b74f9f773d912ef035256af91eebc940db113c07bc65b8
- request
- b71ec9c64a9d77bee5f8392e88e7991ea1a86f22e2cf26464212faaf168e502f
- transaction
- 7a8323a7352208e3b6f10015185ce50ba9529408602a7397bc3b8c7e0cdb66a8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53083
the chainentry 53083
- sealed to the entry before
- 19bee03cec97ff1aa1e1f0df9622168dca0c7eba56050dbba9d4a784cff4a370
- this leaf
- d753ba9dc8624e179ae9d724ec40303f3555348451b2edd1e2647c726a26da11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s5XG+fUJh+bxznYCIxnqlRhumqA6b7uBqqbpHzydlu7TyvZFbNz4CHgISkx0eG7V+a84lB4QRU04FUDuH+CgAA==