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
- a485b6241555acdce6d4645641026afe99ade04e0a4acc633216739e9320db97
- request
- ecc2efdbd438e40307306a5622f647a1aaa7f07325ef05924e61bbf60d74e21b
- transaction
- 4a7d27cd211ae4c9017a4f03120eaba0fe5172a51b5d3af297c4399bfe1b817acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57313
the chainentry 57313
- sealed to the entry before
- ffd81823f867db813660d5e3817b1dce7c9046756633b44a8f319815df46dc0c
- this leaf
- 8f97c2de23b8f3dc9b83bbdc1419092b1816940a64e0e2f8cba3c192b520c727
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XO5g42qFb9PLWw03/drvhw2iLRpQ4y24aEOSCgbuDctbZk79TxErBI5ASuh+F6jNrHkFDgGUNXFPRNV5vQ+FBw==