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
- fc4bba0b9e6f0357ddd491204b6ca77a35bcee461801a134cb84a7b3d7cb1330
- request
- 1f6bccc8eeefe6d7934fc19824103876ff5c767c3f0bc88ee4b6c52c9d10b594
- transaction
- 46278ba81122c8abf996b2639876404d60d3fe57bf3e2adb50e06124163834c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36154
the chainentry 36154
- sealed to the entry before
- ee05be7b85fd50450ca9f6ec99f6ee8dde6530ff7582ae66a6bdca0672f0375f
- this leaf
- 927501f6ecd3f45c90a448fe2b777c3dfc5c8a301e1c4c042400ca38d59d562f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K1qhox/3KwmIN6ARwOLXnUUrrk7Lpc0glCBk+AlG3Q2XYmUDbVGFuaeRWDn3089U0xC3FhLSt4NQ0htzm8/sCg==