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
- 93eaf40c260b39258530d28afae2a0b9c83c298a6cbcdeeb15ed53f9aca4a1b4
- request
- 3cf8fadb5c72291ccaf2ad055ee53a31253d8dcec67ccf9a21d8adc0bd726a8b
- transaction
- 2d002e10bbd70c6a4ace9fa4faf80e2f52f2275765e9e7d82388d8875628f669computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54127
the chainentry 54127
- sealed to the entry before
- d724720bc0f83d0f565f6321ff3b7439608990b97544223deff77829f10936eb
- this leaf
- b50044872d143f478595076570c4a56d1ca635e06d54ba50dc045ff466088435
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aCFN+ndvKncynyXWfEGdRfMMIzloLn+SGuiXd6kGsWSsV7Ny3EdVdEAdA6bjSL+ZudjPystIXSXRBrup3jzxDg==