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
- 4f22ab24ffaf4b5fabd1806ea6264a6380aa7eb108e9e73d9f505ec4b7e7200a
- request
- 91c7574dc2fcc2191af22ec6f1b63dfdd9c161f82703e6e298acb370d1ac5950
- transaction
- 1a8bcc810349eaa4ca92e723200c3b8091b92b5f0a2953e410ed551a85e01b3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34790
the chainentry 34790
- sealed to the entry before
- 221adec0fa6192700314095073cbea2a9b0f68cbc7fa9bc41ad804b6b3470a78
- this leaf
- f5edd3e09fbe80035f56328fb1e6d869db541dcab0d9513409b1769eec9bed23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9ekGIOG+3UagrP3pAdAH5K56ZyQj29EtlPKhLw6bLwEJq1Ert/rFE4QQlw4FoejUJCQpqOR5aPDHi9dZD+IIBA==