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
- b0c1f1abb6299beab45a8b4147ef96e0f8b4ad684971c8b7789c402f181c1990
- request
- c94e36e286711b0e54926b284121222d9e3c5c018bb80e8f02163f04d441396e
- transaction
- 53f6fe649b02e6fedbd3cc9dc463fb4faa6752a655b67ff167583d0179539306computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65385
the chainentry 65385
- sealed to the entry before
- ce02be581e8631a93873f1777941cee749e064d8e445767d85e58ba7b51f0f09
- this leaf
- d0a96d45e39131c89d05b95f36327e7c2cb590bf5711f78223c01974965da6d6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0MLAjnfdpZSggzqhPIysKN4yOYCavUFSA0EMW+pntTZllC6OX0TAsmT8C/1EZZEn/3GuV7xy3CKnz8zAyTEsDQ==