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
- 7bf088f304bf06b12a1194a18d9f0ec9c861aeb4e6cd21187309b631ce3e7dff
- request
- 47de2d777936fb5093d3f0f9ba415e7306d2abeaa18ca428640ceb33e533130c
- transaction
- 9e53d9b358267b3f4af745b171432af043358cf50246453348a28870e53f8397computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47753
the chainentry 47753
- sealed to the entry before
- b77e01e8e9793e064118203399447c74bb6f3d69ce887fcadb6d555ea0b79af7
- this leaf
- 7896e83f327350ad79817983f76efe0d6c93fe0dd982353002b9c4c2a197ab3f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dwzmYyY7ti3CAD0OnoIAqaowgU1rAN4fztI3YpyiRjHmjBADLwSTB5u1HCoPSjzgV8ZnfHSat8H9ACWmqxjvBg==