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
- 65e71345cbefbe070562295c60d8e86e48c246509473b36cf004f9fe1f81c700
- request
- b09d5773d1fba94fbe2d6a7ba0d80f7ee9d5172d955a16efc0f3eb89e1cda529
- transaction
- a6e05815564de656600c5f7504e3bb2c7259d6bdcae15db632f4bca2974c564acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6876
the chainentry 6876
- sealed to the entry before
- b684d7efcc7aa9a6302fa888caa45e60c948127bce652c00c3380be2d2de2b49
- this leaf
- 91ec7eed5bd75845a356925d7bed4b3f3b5a66a229d892b22b2d1e0856afff6b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PRZUjaDFRWRj3Dq0mX5sIYRYWyNLyVqwO5gAwBuXeJ+6sB4/tSCA742oU7hmV32AZATEQ1bqR2nRcm+B1HfmBg==