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
- baae5c6dbf5c98e3cecdd7cce67058f1d8cc1225180152c89632748dd737639b
- request
- 6e58f5ae5387f780bac0fdda0b17768bb370ca499990f2657918c63a7e5db846
- transaction
- 40b9ebb77071a1cff11d2b44c07c56f792d4d4db0bed6d59b7d67e6f4fce7d06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64631
the chainentry 64631
- sealed to the entry before
- b713cb2ea6a1c82938957dfad37f2d326cdf546394acad6264680dbd18c6eaf3
- this leaf
- e32dec2d504669210a621ed97b4e077f0ea2e699a6f0e95779b10d52f56fddf0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- b7Z5cLVU5+BepkP1Kh+caV9avqNePU/NXNLZH72KZE2n13z0ADBrmhPOIqqK0H6Jb/3Bi2EIe5lV+jBr2XGrDw==