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
- a9f0c233cc2f64939387603f379ccf42cf10d3019deb2a693164d57ef24537e0
- request
- 43fe0211d3930645692bde2742939fe855c9806db230c0e7f33310a6f1e41824
- transaction
- ecf08a893b30f1b26fc6459e19dcc49232715a5d8312937de54c04eeec617444computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57191
the chainentry 57191
- sealed to the entry before
- bcda71ce20a0e4547ce691ef265121e1c1e7a8c376325faba37ca8a410bb914b
- this leaf
- f4a142aa0752641cb99fc2b84f8f6e66fd1990eecbcf8630de583396f2b79cb4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lpn3fRT461dFq87fG0Xpz+O8Fol5jSFN5nP7GseoQarZvGW6ZyMnICwCh4Lq76cTW01lRhJDwkiaMDXG/E3PCQ==