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
- 0de830c250933efaf4f77869e1ed16e593ef6688078a21288fb52bd92fc8fb06
- request
- 3f785c9b0eb5bf01dacb351aef807e407ec3f54b85ab8829c20f35d51cf7a7db
- transaction
- 05d5b108864185784c23c217e7c0240d894a0ae10fa583280c2737fe2c80e958computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31254
the chainentry 31254
- sealed to the entry before
- cf0c63831a7e746eba1a6650002c5708865ce0dcf0838aef89f64dbf6d9b5e4b
- this leaf
- ccd31219ef8648def9471d5d2e778a0d703a0d8c6b676d10b272046c5a099de5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /3/nwGJV1/PVtJyQbDxUOIS3Im2X2Qg3pPW2E9sr9IjuKg6VxphSjR4lZGVUXP18z4EsgGbu3VOB6y+9EtfsAA==