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
- 71e773ed660c6e9e5da0161c65a5407d7c55fe412b090814b586e90fce3c9145
- request
- eac7a5951c4f4a8ad0c4926c853eca0358ee6492c1c54d20477220f96f16b55e
- transaction
- 9c0da8520cc20295e591909faf50f8c8c2f2e69ccf6cd2fbc042b2ce6208b08acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43591
the chainentry 43591
- sealed to the entry before
- 5340c099c2d05dadbb96a920969ce3d8b1c8f6ff8863079a66463fc5835471f6
- this leaf
- 4d81447c2c38c87449f2b94eb1c333ea80f5d2ab3abd1b6a8aedb3575e23b7ac
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QyPZ58EQC7xjVwtlvyaGgzZvI5axJuHjymxcxDSAbxFI9cWe+C4q4F7f51VHzgFKGRLKVlV9d2ngAa8WzAJLBw==