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
- c8ce6278ca7be6335595dfd6ed639dd27b9146030e090cb1d900815e2826c872
- request
- 5fdcdfaa338d584902e6292b00bc87864d21198ea512e239fbc4c6c3b7bf30bb
- transaction
- 7599f9e73ed6f731dc599566f084fec072d2c14b7805338d1eff1ce157624671computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12488
the chainentry 12488
- sealed to the entry before
- 4e8e145064b4b1edf4f2a60c23d0c7d6842dabfee6d2b80b0a3dc66af088b6de
- this leaf
- 91ebdb565428348d2a6eab976b0ebb586c2c6f952b3080c054f1d8986ca78c5c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gUIZtbo0DU87myIzgYeCTZb7p13LEFCIfcua0tCUKqB8Ybcd+9SR2qzKBsTOsR9QWdA4D2261s/Fca0baGSPDg==