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
- 07c5c0ac56fad8cf82923051526d9196fcf57b91ac187cba897e8b255cba8172
- request
- 80921785afd0370aa75e8a0d4641c74e5576957dd8627ff1db503ce2679df982
- transaction
- 7a221986c8aec3628688219dbba8077fe9554466b9b0fbffdb4b8172372b5f82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29740
the chainentry 29740
- sealed to the entry before
- 4bb7b3df70e794f0674cd14c3b34cc5eb464ed7c062b9335f2790403c4b464c0
- this leaf
- 6cc7d7439e8b2e90afa826fc3ecdc35746bb9a207ff4ad2d1e91ee2140ce4e9f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YiyshLy97imyOBFFhkgChP0Yw3J/AHSzTNfAIrut0c4zN004tGeMNzIcuQdkP7Z4VZXZqIUTRGxU8Inq2MDTDg==