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
- bf7defdca3ece7c27d0dd01a387dc735774ffc785d238d998514d139a8f058bb
- request
- 61a7f34a36df2a4209d03e75773f69c1a18b76dd01d02916ff736529051ede44
- transaction
- 2b894083457a807cacba7b2d20f155b574d7795c061c6e0e84ccb4744eafbe47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15177
the chainentry 15177
- sealed to the entry before
- 40b0b932ad9a673acd36e35cf0f77a504b6406378748f2b03c4a4eccad3c1d03
- this leaf
- c2f78fcb337f28bfe61ad934044170c9f8a1d0fceeb10f6a4c68853a4145a6c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mm7QMVTjf07xGTC3T/NzR3i09qDadfxu8LqqEMVI9saxGHWZqyZ7NqccoutzJKNUl/lw2K57iMUIZJjOh1dtAQ==