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
- 8b86b3fa9a7e299f5fc345d0e78e20ba077b6b43a9cfadd9c9f33d79fbb2d1dc
- request
- 005e132043706ef4983c1825adb5075e53b00f0d253acd3c25246cbda94f2c1f
- transaction
- 84cec71f30b0bfa61b8fffb5a86acfa83a390c7e799439b35b57bd28a4d21edacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15611
the chainentry 15611
- sealed to the entry before
- 26fee0c91302ad54ce0fcd341b23a3a4ee74cf4d11f55785ae9e369f13d30725
- this leaf
- 89904b3bf4e80795441a0e59cc2151b79dcd73d19bb6d0283e78504313008b4f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f9JjpUbEMAz9bwrubQpvbV+9kkRy4fr4b5TCLTjBp8ieflJ1rnR9mJnbYOTtVq9FmleEH7sGq3HcXDp+vLUkCg==