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
- 16cf308ded24244160a2ca3d83caee91d3299b3a900e0cff5692c93995e73f3d
- request
- 006ebdd27631f7642b68dd7f1fd8ccc3bdc0b2633185749e520f5350c939c433
- transaction
- b8a4b154c22fa05b1b3ed5e7fffd7de1d6764c66967bd17fe916482a64cb1703computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70357
the chainentry 70357
- sealed to the entry before
- 9c1e1b6b7b84f8878a391b0b4221d5d3d9958f3db56c2fd60fa5773e2f32a9d7
- this leaf
- d640dbbca37949a93d9d393d2b44bbcc738f2ae5db4c721dbcf320126040864f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MV8d96/DU3zUsSVVukPnCOTf0RsLHZTOcf9QToIyDhb7mpc1dwOckE0bT2iqJ3oSz4eZDB1X1hZySdMDKgqfDQ==