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
- e49af9efd0ac5bce4964b154ad67e8f6e99b3d385cda5eed0b414d1610d028db
- request
- b15a97b71eeeac87dd15a804bfe93722f63b0e77bbbb16a15e1125d59536ebb2
- transaction
- 2c30d58c275f4a35f6feae0c30075057a677ccff99865d17f40c37415e2a07bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72576
the chainentry 72576
- sealed to the entry before
- cc77a5968251af307c69cdeea94777ec1433a0b0089bb59cfdcb7c83e766de74
- this leaf
- 4fdc14e1604815af054f139c157909d44450a5e07004f8d948f0d7cb0756181f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gaIinJkyF/lhySHeEEb8HfJq4duKAoctTLX/gJiTSWqinBvfI06ZlgwFZWUznYfB+cC/U8VcrUnNmBmwg2jsAA==