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
- b2b2f7ede6bafcdeac2e2f65cd87826d608a45dda74d3e5f3a8091098906f4c4
- request
- abeb504e98b6676b91468aebadd24006c9ebaffb569630a2d1cb83de86acceb5
- transaction
- fb82b0b2f188600ece40e440d589712e869ef55a43ef01e70d1e19cece16fc0acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44785
the chainentry 44785
- sealed to the entry before
- c931a06b2868e3fe1ac11b7b09c039d411cdb0c2ef726c1bb04ea9ef0ef5f076
- this leaf
- 0ac0b54974caad6b865e1f33cf28915eb7ce01b4468f18ce556daab8654254fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zmFH/JeOP0IzYX/o7BwxVUtExb/C1Cy0olnWZ12fFEfYCDMu+/ix9IRZhA3OCdbxKL4JhrIirHo9Gh07WyN7Cw==