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
- 0c128410632460aaa1ed0b3d87281136f9655fbed696f0dc07dc153aa9c6e506
- request
- cbe70575da107de9086b934b9791b1a0f26f2ce6e295ed649ee5864a959d51d8
- transaction
- d567c792bf4620bcd173af6903ad014046e05494e6b61e2ec9796938d06c178ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16847
the chainentry 16847
- sealed to the entry before
- 4c8eeba364b5e468d6ed10b652ec4366e7c24f95f1d451c2535864c6b5380c0c
- this leaf
- 9110ded9e774a8db0d1b039d7bb766cb2f0456f68b5eb8bb14dcf878ff7dad04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5wgUyxopJTqK1GCaE3p2N6afAFaHhtvZW7G/Maff4svvgGrZpRwzx02E0nUUAbLmJ7qIEQShKvnk8JyZaywgAQ==