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
- 4e085c70e40effddfc1d841fe58c568fe54da6ec3018ca77ae052ea54f26d24c
- request
- 427bff7e6a59676dce41adbe29cc88208ea7a6deceb602497c60ed87f6878648
- transaction
- 4d70dab49dc36c0030b65598882d82f040a8f41a2c54b666bf9b5ad3e03f6cedcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42846
the chainentry 42846
- sealed to the entry before
- e7d2d830105edeb7c9d1e800314e2de253f911eaf9a97a6baebec02027792bea
- this leaf
- 3f7cd01e7eca97993cb6edfeaa00d538eef2212bae7842529d418a8f6a105f51
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bbd9Yz40/JvK4gBo+S1pYeMXLCB/5Txxe9q5LCo6+T3bTYrpz34MaRQt9yCpUXfrAWbXfsp3h77ciR8Nw67zDA==