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
- 5dbd2becc87c14416d422fefd822e4299abf7564014d1c472203900e5fcad80e
- request
- b83edfa0aabe5aa70e1d9e8ad10fa27e79fd0c325622ec58aaa05c980ab73b09
- transaction
- 8da5da7d97106bfa08970a43d3b39cd7b432574223c324521e1fa2e5c01c9017computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15698
the chainentry 15698
- sealed to the entry before
- 7f506cfc912acce96e4b355b0c95694e11a410d5322bd925f7fffeb3c19e7795
- this leaf
- 9b762db9fcedd130e9755e7853ceee1da981bc9bdffdcaa120f9feba73a11340
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CHuw7GtcIS32Sz5lwquo0MwdklD8cEXpvXBFinty18gpctL0vBHcfFr0FXbLUreYwRlrmcYBbjB+NFA/stfmCw==