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
- 16a4ed0f98a102feeee914f0a39dcd32a58b2a8a8b80ad69b4750b763dfc737b
- request
- f15dd30dccf111130cd77215e8b3c8aeda1c386469fd7bce91a31a9b5d7548ad
- transaction
- 1c8cf2914f492166189feac6dab76fdc3fbceabcb3befdd98f33f69b9a2a8b36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75558
the chainentry 75558
- sealed to the entry before
- 53b7949db16eac9988bf17a3acd234219730f9283255a01c75ce63ab42431a0b
- this leaf
- 7668aa4669d2116572f20cdff8955468dfd71e30fbe345d3c8e6b53160473778
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2oFOk6XL8z1cvU3BVctBrwqy5d/Iulo1AA7P6J5ovf3KZtSBHYOQkkVHZz306XM/073BXQETCT3kvmJiiJljDw==