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
- 93b39d9a4377e56cb96b69086deee28b6a080e5141dfa2f17bcfa1f4e6e54af3
- request
- 6c90a6fa18dddc6bdeb10cc09288fe3cf287f963e8d557252c2adcb57aed4a7e
- transaction
- 0325edbbcd6d953e0df1e4882ec2558a9bc0a6e1d35cd26f65fc91afb79007b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59975
the chainentry 59975
- sealed to the entry before
- 0bef56e7a079c79dfda146e234d01f7bccdb6fb6727e60bf50560fca931e5fa6
- this leaf
- 75025f35a34ca8c30857dcaa603cbe24467bc27f9a396ea2d562d7d2f7882ee9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HE9rgOVFvO9Wkrs0soalkdkGro2w9U5JDJqpCho8+fp9PDll/GkAbgzzJCYNpu7tpYARGH/Gaja62sn7X3YVCQ==