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
- d848acbf50b436e9cd0749df691b67a35e89b130a08250957dfdfb4cb9584f82
- request
- 5d995de1c772869ee797da74e6c7c24501075a8b6d44cb58593d965a3638bc01
- transaction
- 08bd8340caab6bb488899034a423ac6d3412db238d30898868f6c9184315baaacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32371
the chainentry 32371
- sealed to the entry before
- d210fe72b1e06109b30afb7800f83da1a16f2267489e80fae2b71bfa6aaf9a73
- this leaf
- a2ffd734c8e6c65cf543148d357ad37be01cfb302c4cc5083333f7f26bee5b84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vr2HJnLeAR751kKAoWAmY8UHN0slAwAhX00l+lZudNVsEpMKB4RAWF2/qtuil24ydLlsqR5OY0ZiaMXvXyUrDw==