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
- 6ce96d641ccf8c1ca2ab4359c6582ddd454d38481f245cf324eb99886a945a2a
- request
- 4773dc89fb25cd8529f0ec3b4287049ca9d22256511d6d5a03a4239d0b856732
- transaction
- fcfb70d7a7aebc08c469e29eb338d885fc08767ccdb96ef34d67b9572153a0a9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30034
the chainentry 30034
- sealed to the entry before
- 8250c735878361bf85426c6d4ea40115cfa325ced5f299703bc6ab4ec1f87c4f
- this leaf
- 64c6718337b84737ee8bdfebe48ef726e6d7f47921c21dfd4984cd25ea498336
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- COEiglPmWcgoRTZIHNIrY2X/xAZLih/lXXPWnWPSIGuUeARKwd8WhnWbcxczBdGjVCvAUlhpLEiSoXQvGsWUDA==