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
- 340c4959b63e7a1cae5ce3c798980a7d42395afe1499ca8c3484da9aea6078f8
- request
- 2fd3eff99c98a172ffed23a48278743d0393603c7386058dc14f9bc7dcd2466f
- transaction
- cdbdce46989577039015ec8c7cb14bf271e234403cac44d92311846347f6fda2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6953
the chainentry 6953
- sealed to the entry before
- 1ca54240eeb457a72ba580e6fe16b8c7c831fd27230d96d89baeebbbe198b195
- this leaf
- 05a0d72b7a3bb2639cdefa229068a75fcfc582cf3a06999863ddc5280fe61402
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MLIP/QqkYHV+voOyTjO05bWS7XU+DCVWCuLVgWAayp4+dHNfdCNxcwqGo/xT9+e/BURBic2yEaxlxPaq5+/9CQ==