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
- ff29a7f1da879d5e73558f622a5e20a6844100f00f02007cecb03de4f121a3c2
- request
- 4c00e312840c563b75ba1d0d46ba106ccdb2af951763890a3ae5c60cea0fb472
- transaction
- 55374f3cbee585f316cd79d24d16c6067ed41fd4ee93cbcf5218b1bfc6118d0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2595
the chainentry 2595
- sealed to the entry before
- d2889af1128aa15ce448c18c0830859d0913d523f16d7f5f0e807ece05900773
- this leaf
- 51d9c4300650cdb292f60deb50d7bfbe2e878dd203ad45f1b3592438be9254dd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ub6HMahFCpOqquXRv1SoTwTFgP/aa0jrWyhKl2AWbCnIKbbOAb5Kk+1QMMvAEcPsX2YxfabCZz/ZyAMVmF6rAg==