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
- c04de425b5e86ac1ab7bb9a5cde184aaff50174c83342c6992deeeb9e0cf8a14
- request
- 3c8cb5daba62c50662d929910462171485d338c56215a0a032664046f957bb89
- transaction
- e123b00cf4b9b804e437060eb00fc0b7f156bcbb465759df1ce093f67547d3a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57732
the chainentry 57732
- sealed to the entry before
- 8bc49d44f159bddb0dee6212fee57b64b6ff67162802723954b9f3e67c8b186f
- this leaf
- b46946a59807b113e9e15037233bf6770b17f9ecbce5bc993dcda98db5b78cf3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L2YYvmIp9yVZjpgo/32F+L76B7upEjq651xq0qKL8iu5+vLoe9p3WrLoCEBdPfqLqEHFmvAGEOrA4m7mvBHWCQ==