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
- 2d8068a19eb49468bd0cf841cdf366fff8d82e1990596c2815694cc001c438f3
- request
- 90042421a7746676be341338732b35a7b1a24d1f80506c439ad0be61b0837eb1
- transaction
- d533bb3cecdff4149f175ee8b1aa51d7d44c73f782ab12a861f46c0bc6fac535computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7536
the chainentry 7536
- sealed to the entry before
- 9ecf0e22f0654041898c1bac8509cdc099271c687d5d61eede9ebc55be8dbf2f
- this leaf
- c9c8b4bbe30615696e3f89df2ee186d76fee18349725d9da030c732a07dda781
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5hAQDvbmteZV5mWmIiG/i0z5EWO16Zkz6jzVp2G89Lu6rYniVb4inuSGL4sPM48q54vf3NqY6LSER+IES1qNCg==