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
- 2cf11d3b3e13f3a8df3137b4f3109922ab6c9df700fb4abc134f1a85ece966c9
- request
- cf8364e9c1631eefcbc57fb6716675eb132cb221d8243e4b18e7e75ca190f3a3
- transaction
- d0f71cddf7ed6a9217bd27b5ac3539291471fc11aaa33199c9f9d9c91dc6f301computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16666
the chainentry 16666
- sealed to the entry before
- 70fba14bbb3d97ea57b2e41c69921c60b8886334df3e8e0a7db209fb264dd8ae
- this leaf
- 9ad6c88b90b04bcf9bd85c948cb1f509f5fff6c681b087e46ac78823ea430f24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Oiq3OZAQbfsSBEe1MVM+542IWndPpvvDuLmmwlBq+rm1fP01tbJFmVqEcDe1PWCbifTPVKaTTYAQo6m3dGiDQ==