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
- e3527913444f9177aaa757dce923de820d8ae91d359438acd4fe44e84e05c8e1
- request
- 9f81a59dc01c9c5b271d0e00b50288cb72bd751ce15db5a96d9405388470bd09
- transaction
- 6fe67d9f012c7401c7cc8eb1f652c7460e591f1707648400a78d8e9a548c3f7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56861
the chainentry 56861
- sealed to the entry before
- fbbaba92a89f1cb11fbcb027930e36ac7551f3d4826efd8f3eaa39a39448a036
- this leaf
- 389441dbf3d1c7825f70d00bc2f0d0ea0a7fe6e49c4503632ed7db1b3c32972a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- otnR4pgAqUPUS5mylbARdGDz6a2V1iyTDyzSUovott1zQA7U6MHS/F+n+O6mdLBsh8KNnmqAvvWW3mK8oueYCg==