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
- d15601de9feb5adacc0b6acb35da274925032154645108c49246c78eedbee31e
- request
- f47368b85078bf8427d78570af525a2c8a47664db64f895da2f3d5c4839733cf
- transaction
- bebf76ac0eb095f1674a091ad289dbe238b3315b20ad8b87dcb18bc1af45d98ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65424
the chainentry 65424
- sealed to the entry before
- a5e0f3464356aa61c5f46f82ef290b207c3194b540b39fe11c5dc1c4331e5365
- this leaf
- b169cc4c1369603b6fa7f24ffcbd5c504d5ddaede686ba4f6778d8bc96654f47
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8mpBUfER0MJdtAW5mB4SBplqPPB2TKAmvDJBeD1w0Kss6aIX9xh3tRX3dUDkcCpa0oYIcuALXajgWuKS3cunCg==