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
- 09626b4003fbc4583abb534bfe74a8d8ecdb966e29b079b794733de84b415fd3
- request
- 1399e683916c6569db68c1f3593493c8b6abbe9c5dcb06f75380e286dbcc7d35
- transaction
- e03c1c29db91ef00e581650b5a1c2803314f301fd8b7530262216814f6074650computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40471
the chainentry 40471
- sealed to the entry before
- 98f5f6a3b2dba9b5f55d2692dd3ae81ca7de253c65c40200be94e1261385d2dc
- this leaf
- b6896c3ee2d7da7fa5126e0de8487d94052f9748eedf10028d8d84967f7674bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oM9ijFvncZ7tOIJUXD0zt5KAZKWWRoRhte0021wpC9rZDxlPdIAQe4UU6nPuLN7ZNqhs/GMYAuO/2IKEY495Ag==