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
- f1a946b3db61b9e1d15accf613f00aa22698c155de5f8ea8fbfa52b556d0df4a
- request
- 793f3b05ec6b174dae2d4a871c79eb03803a8e4dae791cedfccce71c265163cb
- transaction
- 029e1e7266520133ffc2c06042c91be01766a9a2a1e9257a72de938bae422095computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70761
the chainentry 70761
- sealed to the entry before
- caad769d2f93c7af1c4b5bd0171c472e3d47507566f001b3e6f00ba028111125
- this leaf
- bc7d3f84e9da045a9e3faead09850b7581ddee6a604edf6aabeadc3bc43a9de5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o3e+vmlK2tdoZJ5qyFmkagupjb9zlD4D8OqWoCnrcGa3mi5iG5ln4z8EZYIJWPIJH43GfxzvoOJq6qRQ+rksDQ==