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
- e1378c1dd32456b3c43687434e0c33340aada72524d302d9585f893dac4fdfbd
- request
- 9e5bf1aa60926c2a52262aca1301b5dab5f92dde5a6270c0c8c101933f9cba68
- transaction
- ebdda18d9ef5eaff5ddd0576394beb083cccf31aaea3b8cf8dfbe42639975debcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45968
the chainentry 45968
- sealed to the entry before
- ceb91fb200b0fccc6482ff8f411418888a4ceab003cca3d96e9a977dc790a7e5
- this leaf
- 99fd361a269c1de93d133242998ede5b82c6eee7685e9aa1e5fe346d1c581335
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gaPDUOEm0O9zmabI8bb+zBp8u+fF8s4Z9mjlHW9Z4quOXJYBoyx6/bdqvU/8eCWi4WmxJkhpJa8Zl0OZQfD9CQ==