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
- 2ab400a738455adb8735513b909356968c8b4d4ab6ff909074cc4ea8ad44b095
- request
- 5c7b0520586d4f8a8616301e85520a7db030b35299313e65087d93acc0fa2f4e
- transaction
- bc346f1f3ed7fac929800b16d71652ef670d30fdb8fa88a4c09e6ff1738ef116computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49008
the chainentry 49008
- sealed to the entry before
- 5806705257c993107aa68696028670366cc0ac0dfb2d2d9ecd6a08e56990015f
- this leaf
- dca6ac24ff4f255c43adbb6e0e0a5d91290fbff1cba2a20b82a15430c311d3a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7FiHOEngEjOOH6biUBSMg5TNh+GrxQFBZt58xp1877pxx7shv8WaH6Es8PlJRu1xeB64kq1miCJ7yRc3OFtYCg==