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
- 5d10bf87a17d05809e45a34e791092dfa972eb6bb82439e5ab3ea14ce72c91b1
- request
- 1ba16e424079b00301faffc6bf9dcb37728323746a8d4a983ba3f142eac4b216
- transaction
- 2533e964251c275e6ace8fae3e89ccb5e40763e9cc679da9d3313f352d1ed3b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29356
the chainentry 29356
- sealed to the entry before
- dcb4c9d32f7900450dbf0890e14ba4b07c6195e067e9170815175136f5bd0d94
- this leaf
- 0507e0ee413660b09fb370c0c916fbe480fbe58f1eb2d56f9484c1a91d35c651
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UI4N8pmiTotBK2KIlMjlna9gSPSmuirKlD1bO6Sx4lNsjWuKQ6MKgD7apjD0iZZFD4DUtLNNTA+MfBOMPgkSCg==