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
- 0f417fa2da204c3d450cbe816f676546e3b979d9fbf72cc22609960a71a1c108
- request
- 1ccb5b7cfcf7de3809461d2907cbcfebf5567c5f2940184dea7024c1403e5eb5
- transaction
- 9597dd681d099439f44d3d0c18e1dde716d546ebc3b88225694516ae0cd897e1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31654
the chainentry 31654
- sealed to the entry before
- 996ed08c5cef375b6d7bc9b4d8481ee789c25e3db65fa48c692acd6f7df45d15
- this leaf
- 792b197359e766c0bb5dbc6cd79f7a889c08573f6ef0f977830c063183ebd69f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3IjEUCAiIp3hUXanu9iNKtv+/OtzbUKD52Ih7KjJSe22lcB2Mi1EC81WFjnoVGwE4gdTdEuqoFBC1BfWQT7xAg==