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
- 40106d33fbf1aa306fe5ac68875e2382002fff4ae5cf6f6a2c97db711b6436c5
- request
- 3807b0085fad0975cc867edc3a1bf60751ccc6bf92bbe6f36600e3f4f3bc714c
- transaction
- 0f86ef88d11da981acffc61f2f3238a09be24dd263ce6b17fe746b9376c0db45computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26732
the chainentry 26732
- sealed to the entry before
- 26c9e3149995c5a2216ea09f7b8f205537a390c14d4dffc63c33f2a8a0495ffe
- this leaf
- f7e89be606d57799c3d494b5831f360d9fcf44c2f2129ecc92335acdbff0973a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UwACJtE4lM1C20gO3b9hRtz5fr//Uv4qgck6tV6XdbrRttmavyZoxKNk3itGNO4Vn8o6NS6P92frkgIMdi+QAA==