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
- 7001b889e7891635b400266b79daf469b0eb01aedb1b7c3a5d300d51823ed692
- request
- b0a53be6f001e68e44ae78ed22cad23b0ed5ce4304a4d305918bf1ebc51e5ef6
- transaction
- b2f6ce06ab66f6d82954461ce1716ae237c32b9a259de539f20bcff15946a424computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71500
the chainentry 71500
- sealed to the entry before
- 548c4d1e24f11c13244fbcdbbdc7a23dc514764c9399779bba7c57b4ad7cef67
- this leaf
- beac86d47a179843a2d3afbb12839ce4f40e015710463bdca7a0e55365c7d736
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Zx7u7FqkWhb5kBttUCFI+JnThT6POKl+ZXWazdA695DftNhrDfK67wIgdHBp/HHA+2dlPZWJBOFdjwpA+R0RCg==