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
- 00a21e435bfbc6191ccf5a4bd6d65695f068b5b332bbf618b225358677a2fc62
- request
- ed7d5424bfb8d303a2bfce3e8717c19331c1e39ec8119eebac763ec0000e5cdd
- transaction
- ac79684e6aa7eb5225837ca3b98d0bca79bf335968b75ff55f2d7c20160f953bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11480
the chainentry 11480
- sealed to the entry before
- 98a9ae91d4f681b286d6371e69130152bd5086e1cf7e4cde823cb3c18685bef6
- this leaf
- 1c151fab30c9e238da96c1f43874d7a6c5cad90c2be07cd5fe3c2854ea594115
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7KV5QmWLvi32iDuqMinXM4O+BUrJFdoKgttJcdRrjoCyHlCVsDx/Cx3t7LVtKFbZNx3oWAbA2QbX3CsALRh4Dw==