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
- 2aa76e69d43b8285817042d2f7fc4f1b98a16da9eab254b2204cdc66c7302769
- request
- 9572833d8f9737b6b3f10c38f7aa7207a269d0220b41760f49aa7bb56d3dfdc6
- transaction
- df901cff0bd6e82337152cf589c4868b3a68a3191d5b561cc9785a2dea71b89ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6365
the chainentry 6365
- sealed to the entry before
- 9d358c3da8814247930a43c4f4ff0cbac7014e687b534d5ce2ca4601d7a78193
- this leaf
- 6f1cd332a9eccc2ef68d075740fd3c8249c8a9c6aefd2aeb51fa4705508cb600
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eQXU3Zessk5CPlsqjl4BQGqpIDYRa4j0H6KgOjY3AZnpMfWZ4AXVWrP1Mwo7TipDEhOsCJuOGJis+nH012kWDQ==