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
- 120a89ffb665f94cd853e89983428a504dffe5e88714c8817acd66dfa3a4f36c
- request
- 4cb45ea032ee725f3e97c317e161c4bbc0f3a503c9d40b6ce400800b5292d4af
- transaction
- e39c9226277d4db196ed402937cec41927f05afcd70650485fa9e65daedba714computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32727
the chainentry 32727
- sealed to the entry before
- 01cae0623ff9e376e0aba899f811727e494441d3ddd8020e630fca39499cda71
- this leaf
- aac07afe11a8c9738f1ed9a9464c20fc44dbbcd4ea74cfd4f8a37cf26f1122af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZRqoWJpVQx7hWl8jVGlzIi82ZPb7QzRhc27q4Rue4SIjg7O68UUkrPa0QYtrx/rwS2+ECeXzT50jGo+lHYFTAA==