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
- 2922cb884e7d6d070ce651d388630a4abd875ce184b932936c69150d80a5cbc7
- request
- c24003041ce1185c3af73b18071e9c335054c9a3ebd666498e01ff59877f81ca
- transaction
- 289130954ce5ab58219119b3526941ee9ed07bceb83c17769da21abbeac66509computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48994
the chainentry 48994
- sealed to the entry before
- e1670c3790600179a7a4fcac2500e47f6f4f7a27820ba55f0eebf55b17bcbab5
- this leaf
- fb4199940ca39b6b3f111eeb041f521f2d4ec15879afd100b5877f7689d3ba8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YQVcnCY5ZNf+gztncMyTecICWDhtnP2Lj+tZfJU6sYaRilUpO+d4w+huYMU/R95cjISFoeHjsKwU8N1EgSBbBQ==