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
- 111dfee0d9052d8de7c9943dd2c3e27b0be14d28c2b5c3bfcbc49521d23573b9
- request
- 0cbd751cb7a0f7d483739ea891864d4102792370bae8137e786f3e1987526ed7
- transaction
- 7c72d9d9b971d387a2ad2eae2d07a1096e25b1572f906b329ae7f7e508530dcecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3065
the chainentry 3065
- sealed to the entry before
- 650951d8e4a9fb524437125eb9e183a17c3d3ade92995d11bf51e0a9862ae997
- this leaf
- 0b2621dbf4734eecd58ce7ef90aae56ed65479715397fb15acf34360b4969412
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w6OKltQ/qTgic5BiPd7O3n+VusG7jOMVtKOf6yDKxb1rwsReNok4Kp7jz5bJ03KTsMlYA2K0kZh/pcQpqK8AAg==