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
- a09309c732d15f722f3df6772028402c84cd12cc2ce7d3de8520b7dbdf45ae9b
- request
- 480bbe55ae15cd7dd78fcd0c4caa945a6a14e88640a8649008a8bb7986234f0d
- transaction
- 51fb2d13798152ea7d7889de35d59cc45cf4f70141036d204b09019b911dc78dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70913
the chainentry 70913
- sealed to the entry before
- 5583411af9d680d0022e4d4c98f74f877b3e9c5521cdd0a39ef4eb0855dd0c51
- this leaf
- b289ddf1571a22ad60bf84a501ddc2d412f0c8f2984238174c021b5aa2d95d07
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FI8yzvY6AtqiAVIlWJLGJf+ck78JMgd8esHKvd1o5LUfVs6fUFV0YBET51tokPhEFxXHIzv7uiCpPmbfN2/2BA==