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
- 12a25729c0978b3902110c3bb55fe000189957342a46f413f6bb8628d1a8c9c7
- request
- 7dd6d09bb35fb4a86a2e7deccb66e53a18f3c6070885ee96e87825fb96e3b338
- transaction
- 22e8083e21dd30369e7a49e41a7158f56878c8ccafb2908234a303c6fe6f771bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24047
the chainentry 24047
- sealed to the entry before
- e9867e37dec8ec93170f111a542d43b511002de8308cd7ca91f71fc7d0ce817b
- this leaf
- bdad01e876868e2d6e900695e8cda22c0ceaef67e965535af562d0c1b974e386
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /+e555bnDVfTE5Z268oI+xl/g1/Xej/GWP+COYnfk+JMIuVYz6NuYc/eke6FGqvLnPXnWWrRIn+urG5ctiQeAA==