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
- 6606984c89764da44af0c57e9b0e127bc8d9c191331be0b4ff5e9020e48e30b7
- request
- dc2d3a788a3f421ae44fcef0da9c1fdfe2da50112a1ccf064fdf82723c8f0f02
- transaction
- 579add92d087db913e65f0ddd4a0374ab18c180987271665b1b69cb87ec5538ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10738
the chainentry 10738
- sealed to the entry before
- bc91a3ff508200445a2159cd8a8006a9aa05aa74bc678b72b8034bb8aa3e810e
- this leaf
- e4ea428292b205b9ffa69cb16814a0f2cc351c3d4cae76c3b639ada8a73dac4e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ovdlXmgOSm1pBe3XBM6BViRCeGajywqIeGIralbL5mvIRPKF/Svths8OH4qqrrEs/xeRNeM3XG2InKApPfz1AQ==