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
- 5cebb3da4b7d0dde48f443b3365ab793fb559e793e309b1435c81a5374396d1d
- request
- ff9606dda5b3156f0e6a26e43e8d0c9f9e45cc89b9248420f747f025b54cc40a
- transaction
- 816552c81777f518a0a53ed6d02120f611e530d338e414ade6c0eef595bba0d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35055
the chainentry 35055
- sealed to the entry before
- 7153513f7145a9eb34812b061ee8be5a8ead873346a8f30cc6467875c3c295d3
- this leaf
- 73bad43fe1fa40bb73b600564325750a6688b1f1430ca4d714e4e9391e06c898
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mX7BArP7rvrtiypa1KPlmVv/wqlYug4AR3jcGB1/j0yjAaGAAH/BaZFVANfP8vMFqj5P+m26Q112GwSu4/7kAQ==