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
- b0a8d39d3b5993a3ed7554a9ad761c82f13f0cb39b28aa0376bad7d51a15620e
- request
- 8f7ca18efac2a42993fce6e14530debf808e13a712c9eebecaf27d1e7fe4cd43
- transaction
- 9b64a5859beb9befe65bebf32cd2bcf90863dd9a772a13f83357ced2ef573551computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65749
the chainentry 65749
- sealed to the entry before
- 1fd7eac5d991ebf2c3a6ff20ff088e8a1ce75d4f5b3d22ee720c69089e9dc324
- this leaf
- d20cebf5c256cb4c87294cd4170ba40d5e96de4f6f4f3c55adda49ed7b22b508
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4Gt+6WCuuR1HIU3g0W9tIMi19A6Aaw40lvwEJatSwqocABAypamoM3iJznPBusrm2lo4bgD0j0IXnNYL+kD9Cw==