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
- b04f5663f949e4d2aeef8e7a79f2b1b5987333658d3b63394a79dc6749377a6b
- request
- 06a21fe1e48309f8cda2de7342c83da25c7b43a610ca5da5b2a45be0b622dc65
- transaction
- 69f4310d1dbf6880701f5130acc765c2b597d627e49ed1c7ffcf98b31b5b6b13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59163
the chainentry 59163
- sealed to the entry before
- 0a32a6b83461f8d7cf2d72e86ba5ea9a5db407d370b6a85c518b1ad08e5399be
- this leaf
- d7b88366fc634701b9fc9841214fb8d96314fee4d807514fe621c99103261aa0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PmzhUweyq/XzlAKS3iaWgULiKo1yBS4DNFhHecogNhUNo5hjhzrROwNcEkOLn6KcVH+xM08FC5dJGJYvPjHLAw==