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
- 3a647a8e6731c97b43dd6e1e07d400cf3830da0d1176f27fc67f4f8d237b10ad
- request
- e07d1264ef56f2ba5d00e4403a0bf3b35cc8f950282bd7770ca010506b9be68c
- transaction
- ac348dc2c05811b90c995c143d3d22b43044e8bc9b35273db3133bd52d023656computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56587
the chainentry 56587
- sealed to the entry before
- 821a8aa719ee9cb94798bb9bc8d210e2f68635f82f9420b4d229567cd0ba1689
- this leaf
- 9f5d3d2fc618734699c0fafc41dae228617f6848d4f1188d1ec72c7b1148d673
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rI/Dq+/sxE6UjWLA9l1naQTAbjyvLI+jUGi5pcKi4viP5kYNbpm2xCS7WjAlqr1FYH8qW/cBk9A4nEQR/di9Bw==