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
- 8779dceb047e02ea56c0f644c8ac6251c0631994e3ce640d50f7cae59e22c96c
- request
- 953ad747ada45e4e5ea0a4c55a21b8904a685289193b3619bed89fa920967fc5
- transaction
- 3073991992863d1209ef88db449ba97ebde21765df43fe5b63833257d159aa56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19923
the chainentry 19923
- sealed to the entry before
- 51e8fe3175840c24c1f2132d861353f9443ad54e72871e8974a83021675670bc
- this leaf
- e0a70ddce2584dbb1800dc4260e28936d4974f475c08aaea56472c0799fc778d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cNBpHqXFbqLDGJ6t5lmAeND9VoOTBGmeRtuQa/IbPz3n5bdbMLhXXc4NJMQAQH0JfchaNo3NoRbPkUlTb0OrCA==