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
- 80940b51ec674240aef90df38f79ac6d5a2e903ab990615052a36dfbeae73ba2
- request
- ce6f9807c7fc536cd0acdb3d5649a1cd5e4b94602eefb7294ba5996f590324bd
- transaction
- 49f701e9c44f23a9ece008473a5cb25d2ceca248901ff6fe474d8eab5fa3ba6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75735
the chainentry 75735
- sealed to the entry before
- 98bca7daaa30d3997a14dea21c422ad93018c019f229d985eff7c3a523297e44
- this leaf
- 4b56412d849c3cc9040323ecbbba9ca003148a34c2ce7c3f407ddca11b46a451
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y/T14W9rENGGeWbpGI7p663K7M8sS0TVmfaFCNz9kum+bsZ3Vkoxhjln9R3qjT9DvLn33GYR+H71yniucquBBg==