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
- d380bec73d9b2f110b68521246bf068bba31a8252a8dacad544765cf18867c50
- request
- 96a7311bee9aa4673119e601ec3b9bf62d53d4c8f846697746470c13553127c0
- transaction
- 50a2cd7456cb351c9b8c2e3f5d8d16a9d9bdc172bbff8bf116562cc8406a7d02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44900
the chainentry 44900
- sealed to the entry before
- fa268f73cfd1cb5b454f8a2d0411426d60f13d5df12a42d33fe55266f39dbee2
- this leaf
- de98ba3e66a7730eba1cdfb64f9be5db6c7901149c968efcdf8c995affe18eaa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0sP9Z9ez99Zj5eoxVUMrahuBUxbmXByOasCef631AoiTfEwoeYDsMXcnqRWM97yRqnmTQDylMbBk0F9JSO3cBw==