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
- 4365f879f8d8a9a458b548396bad9101dd52e7271625b874d36293f583bb7ef0
- request
- 5dfb544e8fa10e11c0c8ba76ddd81485948ee85b0976942f4f38f37f4892d98d
- transaction
- 6323fa38f1f607a3be1d170df323ccafcda24e45077948c65d6918fc7f25da0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77042
the chainentry 77042
- sealed to the entry before
- eae2a4b4311cec2c2c18cd1553be86fe584b2f3f229d5cad4a44fd7426a2bdb8
- this leaf
- 158a4403bdc10ac87bf466c3a4638566c15ba7e619d974a720774a33d0e5ae77
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jV120kp8H0yuyJJOxJJsb5M+H4/29hrarkw9Ow0GsEqdANvQDqES4KXQRiCF0rVCpG4XN6CQcZVRH/j6SQ/eAg==