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
- 427c96e34db75d824a1ed6561175eaacd20b992043627adc44eb9a8863e5b674
- request
- 20512566605c6f9a8814cb9eda948ea4b1ac0489049d62652732651f3eb974ad
- transaction
- f479bd35e3b3ec5807c4344ae8d7bdd04546d1fd5db431eceb91d7431084ee7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13081
the chainentry 13081
- sealed to the entry before
- def174a04655ba6821c8606f5f0b2403d7a8ff8cd3f1448f5e96d4be372e3031
- this leaf
- 1442be8e75a6bc8342711adc2f8434cfab1a9cf01cadab26d06d4deb41e31969
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S9TqDnttztxp9XEwW2DO3YKBG0GUUUFAISihP/GeEVIoBJMKImRAQV5aOGU7g+RlZx2TdHqEMetMhA/gv/2PAw==