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
- a24ada5eec22a350ee6d212cd4108db330fb2962238b5e8a31c7a2afa90be371
- request
- 0fa3a93563dc17ffe7bb7e61bf5146abb369700000b3a14849c250e5b8e13445
- transaction
- 86fef1548db8fc113701c4b6e5a1fa9678d8f17d52a802986d80398cf7491190computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31540
the chainentry 31540
- sealed to the entry before
- 0e7d9ccd95063b18af22ec41c18754681074aac9797358f2777e8727441cb01c
- this leaf
- afe0b6cb374845b86f4909e6d8b9f32739d289a6d4b44bab6f2ad65b65537e80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y809m/dII0k5e66eE2LmxWgPbCRL9doiHo6DOMohttGSgvyusBTQ3Czv7RKNnIjQm98MTtI0nItJGQS5wZV2Cg==