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
- 29f1fe0e8328d33adf7b7ccaa003906c22c4cdcc5c99fa666ab275b34cd239bf
- request
- f6de1dc4bf76722f0cf98d848e189ce1e09b07d15b58410b7603031ba4d6d5ae
- transaction
- e322e4663cde28b8407646903ddfc4c82dbf43a017313ae317b7d84f1e04482acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65049
the chainentry 65049
- sealed to the entry before
- 45a398fbfec6a808625075b7654475d6c354cc6b7462364c15dcfa7a2f4d5a1f
- this leaf
- 02ca4003ea4cb38a95ca367b35b92f424642356f721abc487973a3c5eb6fece1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6lA2ns4YFFXhAZraNI4RGEOX8n1dr/LX+TgQp/OcJ/UPEr0vxaFOw2HbXavvUA7DhKPdG5ZnK072Jkt7DY1rDA==