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
- 4bfd0bfa892841d0bb0d2d4aed5c8b0875109705ca356756ff00a1042aec3dc4
- request
- 4aa904a1ee67e8d71b0a439380f70795b9b7482cb69ef554a6492a125aa2fdc6
- transaction
- 1489a6fbf3a40a67bc7201063d21bd06871b58cc16aea08898098b3dd3363cfecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70044
the chainentry 70044
- sealed to the entry before
- 82999de777934408be04c72a89f5753a8cc3c9d0ea43bbc710cf2ee1625df1a2
- this leaf
- ad61fa44584cd46cba6133df9e9cb967d6bae49973edb1a3921517b333c18012
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lp+asMfHGKcVzUbdp6mktFX/MtFuaXiIlsQrIU/DyV8TMolZugWz7E39m99ktqamGl1RvJYMy25qC9dQvFL8AQ==