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
- a34d5720d55b57843d1c732e66e72c4aec0d661a9b5eae1ede081dcab35b6964
- request
- 53c40a46e45dd8de5086248d47293ab0dca14b066ead278a39bef007b1f42efa
- transaction
- e7e54384cafb4fe95d03143709e1c527843e18a7eaa8d1569bb8535520bfb4bdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20702
the chainentry 20702
- sealed to the entry before
- 86ecbfe7ec2c5b62116be327fdb97fed35d808d8e39e8a0e58a4deb73cd8c6d5
- this leaf
- 45b1001ecad37eda3725919698d3652fd93bedba3c27f7e856505da9529e671b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ugkEsJb/Oc6jHooFqGHpmbwP235EOcmehSUc3lD2o3fK4Z0g7JLYtcr2pvrcDdXNrigm6i3yd9xpuicJ92SRDw==