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
- 6287a23468983b5d461a5301a67fef580896a51d7d67001f2aeffb08673b919e
- request
- df89a9a6f8e11ae07cb742dde88a0e0faaaa8d33abfbb2c19cfb649cecbed8be
- transaction
- dd5527851fb6f82f718587ac6ee6e87c451b84b8c260bb53ec44daabf152dd4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63084
the chainentry 63084
- sealed to the entry before
- 1161385034cd3aec7ecc5e7d0b95434dee6cec017dfd36ea0eeb0b1d31768dc8
- this leaf
- 47dfdb36d2b1f59dc4744ef8fb75494064b90b8b9bb251aca756edc7610d5f34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kvLSGKAj/U76ZTvttUPzz+xv+4sVhoNdBkMit67Fber7BmFNH5b+5uNU08F0hxLirtaZ5chhSy0Iv25Fbq7ZCg==