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
- bf6e9624d2031f141a59c6faa3237ea19ae7e8a1a5c27787a3b234434ee11475
- request
- a89790ba5faa8760d984190c53f7efeafba7a4d6812725a7b78fafd6ba6ad160
- transaction
- f11bf804eb7007dcea686b00ca396ae5baa073a4ddfe4488255ed66720837a1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72191
the chainentry 72191
- sealed to the entry before
- 0067167901a41521f4456ccd86492fe43c67ad47f4041c66d84e5fadf242b963
- this leaf
- 6a0042f1e4005184f3e71d8e783b9d7fe0b8a45a7912acb2b4e949dd0128444b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mNaJazGLL6E2XNKss2TG9b38bouiYnJFuCsh5uEz7DB0TuV0Z9bLo+HA4emVZYuNp9gzqb3+2h2aWf0LacqWBA==