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
- 9c0fac5603e964f6c003a725ae23fbca4678efa0bc6e4aeb5c1ccec80fdd672f
- request
- 91c593fa530f6922683c022e31ebb338a96595e4a1f7a1371a00a288a7c4206e
- transaction
- 9f0b7ff83bbd7f25f5f5630c07c3aca14a53fc70413b966b0edcfab55b293f7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39068
the chainentry 39068
- sealed to the entry before
- 9e5270657ee4b229c6b0ea223633ec92f813ee13a2112c6b9b062b7005fe3817
- this leaf
- 67b3955369c8ba4b6d0030e1badac2f2cb19a569823be8a6d8f822f220b62e1b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4C2Noy8gHbka1gvy1x3AwGXKTJ82frDMRMdTEKxXgaZj//9UvEJZmA/Jz7pMvoVokbs2/9/JcRODf8Oc1IivAg==