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
- de4c305883ec4601ba52a92202414cc8767f884d18215093447f7d41d705ba37
- request
- a6aaacc6fb47fe16e2132f7713d47e0e69b21606bb683e3268c06f99d7856161
- transaction
- 99fe92a9d502bb00c471ea128a75a66bd865bd4b7771d102e3ba029a58093e12computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18553
the chainentry 18553
- sealed to the entry before
- b7b6323bfd420d94eb3b912b6713d9360870712eb77902031f9da9c892cf6608
- this leaf
- 1728ff4efbe3beabea47f1ba50254b773d3b0eaa20a14bcd6f836b50e1276496
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V62Zc6CDtSRoXsLE1jzcqhwoWWEg91PJQdLuNN2WyA4crBJgA5z8Aymqmvj6xGsIU/eJM5PRqYBPQkzCJlNeDw==