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
- 2b64dc7b4832c4ae59f4dec9a952f180c75c3598156844a2af1a194dafd5b028
- request
- 55fba58270cec66be790c58ea43e15dd48f5c8eb8583b0167999f543400ee4f2
- transaction
- 22e64771da21043215e60eab01049f8aa63aea33049cddf4fa4e61934988b7bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 59456
the chainentry 59456
- sealed to the entry before
- 2a1e4086977ad0b19ed40439b0d349e930c191436965c05ceacb21f2dcaadc79
- this leaf
- f7bd6355d46c912d8692efa877f173fee25411420509064b636d0aae6fafa3af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jiQj+bZ2zrplAV8w0RlFULvumdfqZrk9cktTw2TtsXjguBiOV69LJyk3+RRM7oV+U90mibC639sq/1oeK5egBw==