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
- 0d42d34684fe2de4602b2e3bcd9753aa9abba83f3f58fed8fd915187514effd2
- request
- fc6abbc2340cef94ad13fcedaac2c54d747fa02f2ddbaad4a2ff96e31eb73e40
- transaction
- 62104f555c688cdea822efdb752e03dc06fdc456b0fd6fd2a8928311f5b47d70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62077
the chainentry 62077
- sealed to the entry before
- 563fb514f9a0182f4208bceef2a083ea470cade142d11b7a123838f7412f9d13
- this leaf
- 4e62b26a3015bb975dc153917c735a228d0ebe7bdaabb0aeb8c0cc677834759c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BJYZAhDcej8kvZj+eI3KD91b8OElk5we3FomgGFzTfK+sjRVkJCXD3QxdGYNp4OyBFxAJ9Z2i9uiq2zh0nFnDA==