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
- bcbd519524b017290b882e1ca75d4cd56d54531eef00f710cf00eb1e34c79fac
- request
- 87cd368cb5255b62ee9b24a2e6104576dd4e05752f1bb3efd4d45f60515871f9
- transaction
- 20ebb97ec5c6a40309b14f71d3a05286bd629615aa17e52d11106b7f779c8bb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47192
the chainentry 47192
- sealed to the entry before
- e231f854b46a8843ca35326ea92f6a00c24aa91bf1dc32b8f3ccb71a53f41b4c
- this leaf
- 4821b3c8ea6523134aa2375f4670fcdce12ee7bc0b22cd8788775381a555d5f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lBkrx65qXjK++x6ELmB9pcxbIGB+wiyRjrBFdwiRs1iPAPiSTcFTdeNSaevNEOMMqYt0gZzom6AY59kbLA/EAQ==