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
- 1d5164aea5f02da78eee2c19b192886313e81c7b478c66a99bf2ca72dddd475f
- request
- 29eaec1a45cb710e35b3ee8c7f7762efc83095704c3f12928c781a6ec5262265
- transaction
- e81334c8a3b436c2ffd4b9cb8f2ae088d35aed5667cdb77bc32d718ab88afa9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46437
the chainentry 46437
- sealed to the entry before
- 8065a6e0e36d47ec284526b6e3aa50da7a373c484f7e37d9022531b4c1ded377
- this leaf
- e42feb68442f414c299fc989de78b55dac570af11e7a35779bc8379f77063c1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ifMbdMbW5xLTTNma6gs6WvHPeqt2S5466468dSA9s/PEBu9QmNJsotVTtNHTjgfox968iT6R7PSeOBXcHyn+CQ==