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
- 282bd8bca516d855029d09fef1de5b82a7584cc354e65659ebcb1880a2f1d2b2
- request
- 63c78ca2d4e5ff765ac3bdb3dbfd5807128ab00c92597042125fa4de98a285d1
- transaction
- 1ebc40b9de71ce67952f137b02a1e02d15034f6a133bed486dae779abbd9e7b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38258
the chainentry 38258
- sealed to the entry before
- c1e4fb15d8f67b012897ec10759dc92ec97ea89053048d2218d1ba70470a536f
- this leaf
- a80f2632d0a01f3236949bdfe92003d6e540cfe4bc998924d774464bf21fe1f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +nbQTN426EFHXnDCZeVzB65m2Xlg+Pqket4Qj+dfO43VgQoUXVhxf1BgzM0I8Uiqp2fstXPgC0MrohiCPTOeAw==