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
- dc82703499e30df0d287cad9dad661091626c3ab4e016774d688fe9d2dd7d162
- request
- d9a811f7089cfe774acdd4c7a2197721b2578deaac07d02a287aa7f850abf621
- transaction
- bf43982fc1b9b3fc83137f8e62dce00e62a6f7786cd65eebf75263690d12fc83computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54914
the chainentry 54914
- sealed to the entry before
- fb371e1651db45f96a51236259fbad9c8ca2f3fb9677d18a4edce9d4f02a1648
- this leaf
- 5b72400053242772660e28be97e7321966deef0f6f315d4e407dd1801d39d002
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tCai1lnOv2tyKA3L6EMGtwZHmQ+Uuy9a9Sx+2blWQGaghXmXeu5G6uAJdWiNPYvpTgPXUjWpqJeSSZ+9ypjNBA==