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
- ae6cc1366220f7c5492c0cad0707decf641e33247567bf038ff5168b1e5dd2af
- request
- 8d44f84bb7a8c75fe2988f8b9be781cbcb6d27bad969ecab7d59e194f7be4889
- transaction
- 2ef817ed867d669a9eeb458b4c89a4e4ea1b3a58d79365de7c8bd255b3c23481computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57088
the chainentry 57088
- sealed to the entry before
- 0dcd531b3119a9983b7fe3f7b116a992aff8a4bca424f2e06b0646a36efce7f2
- this leaf
- 0f4e698073635555fa51f0d7d062bff32a376d7eca7416de8b37f62b44acaaff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yN42e7uuWS4TfudRh2hk6TQA4ziSWfAo1CYz9lhxjt45ObGTlQqkbWWlaXci+LWauRraErd5827n9fMDwTNOBQ==