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
- b37c4651794663560405102dd1204ac282f6c9a89aaa853008fa767fd7816755
- request
- 6144b1e53674308ba68a99cc0e60a1b8508033d76589186c51a459eab2e57697
- transaction
- 0e96fc4403aade4d418a6490979fdde67d55b7641596a524881c30ed99996252computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34868
the chainentry 34868
- sealed to the entry before
- 90d190c79abb7f790be70530136fae7e6885a8909e32e7e7f33e2b42fc89d563
- this leaf
- ad5ad8e0d672fffa6ab6ebdd45898cbde5f411cde406ee7e13e3231dcc264bb7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1vB7uVmD1gQbDrHYFb9PoN++q+EK6qVBcWp0RRdCWigcstuiHekS/HTijv2OupFzyaD1zeIFcyCpWcE7D2mDCA==