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
- 5d6f340517fcb09960b78b6fb052bf34e711e88cc64d9a28cd2b203b4fec7074
- request
- 1626218359e8a9341ac16fa9ec5a76da2d2852cd8a9d8656516035f8c02cf694
- transaction
- f6d72a435554734789f6f0c06e0a02de1cde3f61e1ef1e155b0410f5beafcfd0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35223
the chainentry 35223
- sealed to the entry before
- 6224c63108ef246b866edce316feb14cb810ce4d9fcc50748abfda97da9c0048
- this leaf
- 642fe15308718846be92f0d7b587622e6c6b14633644a160d252e8b3967b7bed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 58azmzkjEC0SSIL7rZ2ewbl3r2nDlRlQgbJG55IdIlNbbwDfWeErOnvmTmlqwTRKr2Qi14wbir8+n+p4Ti2HCg==