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
- 31561aeaf2ca3a37182b19585e8b539b7de029334bea259edd314f52dfc06ca8
- request
- e7d50b00e320b051933037e255d4af832585e9deaa8c18d590c5cd48044aac7b
- transaction
- 1df8da545903e8045f074c462c07d7672cfff6c6205d571cd6647996b615fdd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18175
the chainentry 18175
- sealed to the entry before
- 3503a84b2f5e035fb235aa3d3315789cd46cc15def0166390afdff98598b65c3
- this leaf
- 88377bc4085fcade11061119d09b978ab46bed530dc811e4b5f02bb9dfc6c9b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sl5CYwbRGeEsfL79nrqMfAWWtI52T7usUk9lnSK4wtmW6NVkTbi/jR+A3nLtddRJbKztp1QEyIOLXas6jt0nAA==