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
- e54f4b388b78a2080166e98e88562cb549c259b1a55ee8b18b33a3669db92456
- request
- c62e067bfb846251de4a84c21b78f3f388646285514e8a9ca41ccfe3b5a071dd
- transaction
- bd0d9e7fa53858d7a651a2dbf9036ec92de3953aa1994ec3482b90f9d316fa48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55055
the chainentry 55055
- sealed to the entry before
- ca43e8cc30a2145fb09680a336c0b7088237f143812e749bf8bac78b9af9028b
- this leaf
- 7ba7f73a3083b88eafb89a6ca0c82cde1356bbe62cc28ed7479be7016435aea6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kzxFcvFa2XSZAIUBQf5h0DpgvEfhpk3gEa2Hjw2x1vW2dQ0z6esZ13/Udukb0+FW7ItE84OmL7GU/eDWXgUcAQ==