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
- 37659eec828a52ff69278604385e9a7e38d267ec526d0e4e3209866ddd9484da
- request
- 60eed21bca7125d109cc02eb95f3a875d0356caa93173f31304e0d63e9238a0a
- transaction
- 18221dc54a0e5f2b47582de8101b02ac8ce2fb88a7054a509b48253fc04e427dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45198
the chainentry 45198
- sealed to the entry before
- 0cc5af4e4ed7cb3ad60aaa64a6092b654a1ed70735b9500195b9c0aba8b2c20c
- this leaf
- 825987d46bcef1b951e15d0a2fc1eb90f22df0974ee0deb5396b425912935dad
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e7c+k4xiIrnt5NINTnWDr7hdKMiCsz9X/mIibXF0qK0QpCdTsAUPtOIFyc1leRlzixOBajle4+U79xCjxfuSAg==