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
- 717e9961c114db41064cf2c07c5448d0e6406a5bea0f8255e48c2bedb19ce1e6
- request
- 74ed8be2ee00e8711d54afb2c0dcbee584a4059416a2e63d39e1f5f3f23d2e5e
- transaction
- dd1f576f7fe1bdd74ad08a22951ab0fbaa0da97e48c6c79bfbec6c1e2d6502c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56168
the chainentry 56168
- sealed to the entry before
- de3a48fab52d0239a6731fa28d9b6a3ce3fd1cd51c647ada4f5c89d4d6937aee
- this leaf
- 5499fa83e4e22720037ad04c750d545c9bac1d54c148789e59af0818c2f9fa9c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U4bgfRCWMXlIWi5np0APWk1JN4MLdzuvIwXOH2DzKfWoshsbrNWuPPe8oRtVgDI+Ovpy7PdCPMETnn4KCWoXDg==