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
- f48eafa8066c3624e0a022b21de6f7ce4c9e4b631a8000b4240695feb84fe255
- request
- 291b6310874742a6407dd7b5170ecfcbbcac40616bd3fbe0962861a08bc6996f
- transaction
- eb30c96367231e51f6968c83934e67aeb5ba52ac6dd8fce763c653774aac3d71computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27314
the chainentry 27314
- sealed to the entry before
- 3f0a4873c67bd46901d493e7a6fdc5cf77728e4d7275e05d005c4581aa8de6d0
- this leaf
- abe9f59a1a0570278fb58100ddc37cfc1382eb007da8e69985b77eb1c32f9a3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zck0FOvyhJXlbkfzfmAVlTrIGdfRkxAp5a80mB+JAaeds9cg93Mgw+ESwm7iFA4ZVAQUmwUlgeM2CMMBqyoZCw==