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
- 6aa46d8fba2e81795a1e62dbf39af72f8e56b35b7efd92a407714b08f78ae5a1
- request
- 7983ac61bb9fd06cecc5947301cffc0ee877028ab2ddd109e9c17c3990e0031f
- transaction
- df0d79687067768fc2be3d5dee507956ab15dcf2df63280aec67029cbb5c4a61computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 851
the chainentry 851
- sealed to the entry before
- 99b3749847dc9a7f5bad57210a3a56e6b5e7bc9c2d7851b1d2ea21d19449d346
- this leaf
- 9b5fd9a91b5885a1b7ba746e1c3141e56db37db380df82e25c746a487d8b4a3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J0nu9TSJCc/vwI/6Fg8L41eGa8Z7SalB/VcfnvshoOiBWBIfpzF4PDTYr0jJS3DO5nS5rVBaiRNeWXD2bKzvAA==