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
- dba5f9bf216900b1eeb65d8be2d7945d48f918b392519ef392f0ba11a9f7eba4
- request
- 73927c83afe4f185cdf8abf2c0da87b7e814fe2c5f978accf6566cd26ab5c592
- transaction
- 5f030220e37f00a56e75c234b86420c40247383e510a3983a92492dbe54060d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30717
the chainentry 30717
- sealed to the entry before
- 92103b7168fc1bdb748b7d4c3c9a0d8607ec49e4e787b9628577686a3ca98210
- this leaf
- eb04983a2892ce33f50011f4774bedd851929cf382e4840e08df4d41f3f22220
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PHT4bBMaSPC7kwoDWaSgXn1tC1fhgbp40a+qsoqSV8MxIDB8o4k7EFeeB1OpKQnidVrVN7WCzngMxaJStrhADw==