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
- c57f0f9cd9465d0abf669b2d1d553840ab20743f0d84fe2efdc1f07aad876b93
- request
- 47022bb5ec617214de1eb48b4517a86c96cdf7ea4a4521ddc89dcb18e92df814
- transaction
- bb73e44c45e0e6e948ad433362dbb523856f91aae165e4abcb4170ef949f41d0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2165
the chainentry 2165
- sealed to the entry before
- 8c86f8ead8da1ee206d6d53d528d88e7d6b41df8766f83e580fc1aadff18de76
- this leaf
- 92832e283355238abd7a96e5198bc4c82d55ecdc506b7a9e92db25c0332d560d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wKN9wR4mT4kqJwNvDyj165VMNFlndbsgMgfT0KSm2FfpYKYebfobmLlzB8oOJEBa0XcqF5zmsmjXWdSubbqeDQ==