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
- 87477ccb52f8a16c14ef32ccb29c712fc96cd54946163ae286e658a9ed83979d
- request
- 332232898097316f379001cd1177cc89b289979fef0222c776f3ae8eec68f10f
- transaction
- 9b8230c9501f369b3b1276e40afff0dc2d96d22f315830ff5507deb8640e33c7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16649
the chainentry 16649
- sealed to the entry before
- 0d0c7bb89c3f0619db39794a62cf020329fec9bd9f18706ba0f55877e58c3c6b
- this leaf
- edc5b907ca09084b6918e314d22fceecb8c49ed3253630481d6700e9a4964344
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UVGrbCuZ6f9xAeONxTq5Sd+hmWY0ilfDcLEO9ZecaHLewwrZkCbOkgrQ8tOaZoJEGtp2+M7Hiz6wegDVust3Bw==