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
- 0102e001652b055b3ce3ebab6e856258b8065f613c3fed73fa28646699555fda
- request
- c42db1f31129295a207eb66c961167f4d7563fe77bfca97ed337e4be232cf594
- transaction
- 9d7e57adb21cb0c93d2e8005d82b0d727aacb6f88fb96aacacbeb892d83b0f89computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71300
the chainentry 71300
- sealed to the entry before
- 8a8c37764a5e699d707d02e2df746d81cef15c569c051992ed407d072b4cb5a8
- this leaf
- ef41a71038ee7dba211cb0f4de7af5545a82481e828f0c9e4f078ba915fc23f3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bTjfuAiTnyUzK3czSOFTyuR/1jV839KxmvsI0OBH686MY3gmF4vEW6ZgS4OMMAlS7aLVYxTqw8mjnUgFgeByAQ==