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
- 20fd78c77a8a2e8a8aee36510034d1f9430a66945ef105671146cc9e10e833ab
- request
- 95f91e536e4562505cf2b6753cea484b513b0bd9faf639d57b5a785c2cd8b935
- transaction
- 4662a7928653c73e067c72a36cced049d53ae688143d7533f9808fca90c47241computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35641
the chainentry 35641
- sealed to the entry before
- b3cebfdda4a3fb0aac5051e50f0a8449249876b8a3f0bbdfcc3bcb4c82e44536
- this leaf
- 37ca4e3862237f1d5274150464944eb118f7dd2803182ccb6fef7a46a088cdeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dvG3TH1Hso8HyKt1xQU7XG18q6+FLjO3Sf+CjlyCeNCUnbIvhmfQ6fjHDHHyUJstIE/ODo9gxQTcK3BA5rp3BA==