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
- 1000506d439cbacc7a228f14d9b569817760f553d80a2f63fe9859c6312b8df6
- request
- a98dc345e4edb10f9c61b6e7da763678e13d2e967a39925bd23cd7bc9b270062
- transaction
- 44d20858f5bed2b1fb0ee73948faad1d5b104f2ef3c4230186f724095ea9e97ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64002
the chainentry 64002
- sealed to the entry before
- d28c0c9c4d89a6a8a7155b147fcc5c453f1426c33c141fb7bb2db62cdd10e9d5
- this leaf
- b7854ae35f791f91665a4a4ed6be8b18e07b9cbbc8a9bd5bd7d02bfbead428de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kQw/n9rHux5bytm1xgQoak6V0EjB2VZ91H8ta6T9Guc/ViaVt75r7B++Uc6JCKhVhJs05dq8TfBtDjQEEmVNBQ==