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
- 9873a17a2afe379693fdd45596aaa18c68310ee080c67a9ebc9c3ee6c5e28a06
- request
- 63538a340eedae4f058ed9a11c3c971b75693e4f3de6cdad01c1678c2b0352ba
- transaction
- cc31426935f33759301fb9e4679d252320a3f4eae04671361bac357eaae4ca3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40653
the chainentry 40653
- sealed to the entry before
- 8f9caba7789476c1b528fb2a3b0ea5db2c1a5424d82c2d3db78cb8193f655293
- this leaf
- 485a3c3ab2c25ad0f07379689410dd0bcea2cca8f86e51f7a8f9f3af6c4abe1f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o5bfNhfONKzjLhguuFKvR7Wil1T7m/hhB0Kd85pWquouhc2tc+GjwQ4jzU7oXsn9lDibTY7NwP+KQkpBvK35BQ==