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
- 3e509a2d227d37d4aa7f22d8f4040119d8f52be063f271e9cbacbe57b1799fd6
- request
- e912ac66c7d7b5350f7038d90896437edae485528f421da1dd7ea3aa15f95ebd
- transaction
- 3147c4fc936bcd3f06120ff4107cb632a51f89831a1f3a8ee371c2acbe142ce7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47486
the chainentry 47486
- sealed to the entry before
- c4da112b982eb72e5a1052f4fba78001d0ae1fb9483ed01885bd05d481fbe791
- this leaf
- c0ad11a40e51850c94cd8e25a84507e5a1a78f982885d03df89898311cd566b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- elW/wcgbPKWjVLcHl9Gibet4Me6QxInoeQ8smgNYq79vgM6kZTeb27qfSOkiIrd4yKlGCksatV70LvfKiWuWCQ==