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
- 28fb2cd3cc877df682c0e58ea73bc06a3a47e29e337f5fa60fd198a850603ca0
- request
- 83db9bbfc54c2f7ed7c23c2435b64a1be73285fe7bb8930f68bdc59386e18815
- transaction
- 814c6e6c7f3bf78f3546de4fe25d1b6a70d47c1af0a26ea58031d17c40c36b9bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65318
the chainentry 65318
- sealed to the entry before
- ba8036fb26100397794869611eef2a1e1aacc9b9ea73950f833b41fdd77afce6
- this leaf
- af44184ba472c0847b6e43e78b22dab1805420ca27dc86e9fee20a98cdcec6d4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bDUOBTxrnB/n5eUqMO5KTK59n0nyJVSLrPrMviCPc1ls3A8ks28hDLQdBlxwTGXUF/EkrOT9ptJ9GBVXc5UdCQ==