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
- e1fcd5d5c0bcdb1bfe8a6a1b225604f90a68eb2753bf36be83963780560da258
- request
- b4ffc75dfa21335ed86562d6e0ffac3ddf5487b047d2f4725fa05fddc05d7009
- transaction
- 4d8d2c0c713cac8364c58f8aa4908f398f26f2f29b13b6326df654dd5ba818f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52033
the chainentry 52033
- sealed to the entry before
- 0255e2a4894bb58836c2746a62bf7408959e4bfa0fad4dcd4e6a9c2f98db3d08
- this leaf
- 1e2234bc4be87df62122fdb39dc00a12c390ca09496b34c5805b632d2504abbd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v/2XrqIKVUafylWu0G4xG9k/5yKFa3X3wrYc90KQ6aic6vP4i/2g+PRaZTG7sUtSn5u41MMNJeOjrukgajpoAw==