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
- adb36a45b0f319d69070eb34e9d7c102fd2c15a24e5a8edf6904f487ff779b6e
- request
- afdb14430eb92a1bbbbd0e43b31ac136137c5ad9c680588cd9674dc1405b0efa
- transaction
- c567577f20f5d6da63ea8dbda0404f1bffd55baf14d1f2dec55d2a74ee2d405fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30866
the chainentry 30866
- sealed to the entry before
- 9d913d6e905cf728874ee1701b8096f6a07cce7db83b755a69e1f92065323628
- this leaf
- 72fc4ad6575658b4c9e4ca0d67fdc137c490dba93b3e7baf295ca1f5cae606c8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e45Mu3RFuMfv1ww80SMKj0lXFGyuNJ2Gj7fSFzcqH54EdBHb4nb5BLPrdHt5JsymCi3n3i1GCaxTUGu+ZgS8CA==