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
- c6ca54d1f0d71b39b1cd0aa5535a05f614d536934fa15fe60518ba7ce28e4802
- request
- 034415976fef6b6118871c4ef908342e61a11a5684097bdc87894f2c10dec9b2
- transaction
- 69285ea4b4b4459e0b3a78f9f4d62a5c10a05ca161d0a8a84e4923bbb581ab63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33755
the chainentry 33755
- sealed to the entry before
- 4c948e3f0f27c011af3c618c93a1fc42018339ce25bd4daca10d737f7f03f23d
- this leaf
- e358013e9b3b8aeb8981c75c0b3d1447886a8413affc4946d7eabb60152db5ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oAyFAXpYWFgEwkp1PIjB2tzk7LkUEX35GGx7xW8OwuE710xMYcRmlAa+HRKq5VQQ9H0vHQ3xVHrWOazg7yo/AQ==