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
- cb3084cba8b96b0e6fb08580a9122b00dc91b00df008af72c832241a573dd775
- request
- d5aeb80b27b02a7e82f4c060b4c79fcebe582c378beb9ab3101fdbb9c7ee8287
- transaction
- a6e662824978e23187c384a6d96acefd03d3bf5295c3b06c9fe15b21e683f427computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57247
the chainentry 57247
- sealed to the entry before
- b2f863a045b62782b8b47c2aea2fe11d96afc5b57c3191212a3c6edee0d6ade1
- this leaf
- 6fed87b295ddeacd63d05b6d5ff9bb4d04797fc8ed68d75a7e8e709c5de7fd04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6M1WKRo9KFZfEt9zqu9cPFMa3LsVGL9ekn20PzURwA9DSWtS/cF2QLzwZ+CoM41TFjp53JOU1RC5ODv1uA7fBg==