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
- 840834e24d3fba16e80c7092ab6acd4a80e4badc0dc400975844bf0981ca76bc
- request
- 4d1bda18da09d0c0a12b76ccdd2519c5428a232f7d24db55a2d4d099a939bad0
- transaction
- 64744ecde3b893ec1de9ddc41ab79d2cae431db9c8c72b405021408b8c962aa6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22986
the chainentry 22986
- sealed to the entry before
- 3bc24d27436e7419d9d175079bdcd34a6e957f8224c10dbc46b70a3ca8d362d3
- this leaf
- 55fb6565438fecb43927cf2e1df49f0bf3e45b9ff1ba25d499c1ae16f1a82e56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mTrvbZGX4O3ZIU1XpPQk0RP+x9vuKowOIcbN+8qSvq8aRKK9GgYkJZPWFGD3poUTaXnF6zHSthoW9/YWJ1UGBQ==