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
- c239d803fdf2849bfa2cf10030fd46397fa0145a963baff2b01d7a1cf564c7b1
- request
- 2a0ba37c8ba6ab05412c0443d7d4a5f697109634931ceac295478498e92a9da2
- transaction
- 6357639c0bb0511f2be649183e8257238f0a0f305e320a026d6197ffd5d2d83dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10004
the chainentry 10004
- sealed to the entry before
- 44cf299485b076bcdaaf4f16bdb9d22b23f3c9d83343a9aa805c104ba87e6a0f
- this leaf
- e7c262b1159b22ed06119985fff79bee3826499eb9fc356330c60e1a4bd4a312
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- t58Q3z5BqTx2qkiPT4Pm4tzzSJmvDEDrS0kg80orvL83eeeI1NdXY8b1IQiMx2pExutyivzHxpx+gjE2w2rCDQ==