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
- b4af9ad92fe6abea43f51b6c25a73613bb6c5fea605e51611a2f11ec0e76f529
- request
- 745ee46629ffb6d45ca86deefe7965a55105d16211d346b83a128cc41c5a0501
- transaction
- 5e810c9752ed51a585af762d68bb227060767f49237f8a84940f6472274fcafdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56873
the chainentry 56873
- sealed to the entry before
- d680b5dedd8c9b7116f7808a37d2d1e3f3c92e3805c34089c399548c0c59a8dd
- this leaf
- eabab0848d4805677b1b20cdd75e2fa93ff6e0b700c583bdc97e7e4e72aa2dba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OLglHSlCJdIfoepe9ke0JdsQvsXK5jWx3KkmQsDmbV2ElySrlvf7YLpPjCqvDkamYh5eHzpG56C3SKAWx3vBBg==