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
- 70cd6596e8d1ff86e59cabcb17e4601a0921bdadda52d9e2e491dd9a94b8df5e
- request
- a0959c8adf935e0c1adb65326144a55266aca8c9194f54f232df8d1c0266294f
- transaction
- 43baec1f79ae56c6afe321021d5c82fb644ef8898126352104fd6b39d961ddcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55060
the chainentry 55060
- sealed to the entry before
- 44f44295f7fd9276ac72ab2356b477b6f59c561225a6407408312ad8266cff45
- this leaf
- 1e7d53a92242921dd6360e58eab500ffec1f0fef856226aed9f1b328e560e595
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kpf4WHwcoEzac3fz/PyQI7Vq1tQu4lK4EooSE/5fsxKJ7D9OIzm2dxSz3oiVevbp5ZM5xJCMIemXlv68zMTDCA==