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
- fac5473761f8f61d1623408ffefdc8d3a5616b187495aacdcac0ed0e91919f0b
- request
- f8ea8d3f4918a2174de695f3eb205592b76606f0d47fea87cffabf9cd691439d
- transaction
- 0702dc068a014e749abc38c2c6d0d76cb972061d1363f4756878416edbc329d1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45438
the chainentry 45438
- sealed to the entry before
- 333c96d4406c1d512881c690351ed5afbfbe86d7822709b127cc4c0034c505f6
- this leaf
- 87b4983a0bd7bdd104994287c798ab5ddddc3e0f9ed362b0846f65ec112fcbb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MOGrDZAA5n2kMei/s1uadt200WqWOcL43ppmmHbCDEgec8DwRyXeH8GVc+RgZo5IsFqRKbeKThS4v7zBodDQDw==