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
- 1cbb6d0de1a42062e763a4a8e7fb3adfc1036ad3d9d88563fd554a1e5e922a83
- request
- 8d811d4370262dab171cf8eb89e32f624e3478b8d8333a3ba9f790dbaaa27f0b
- transaction
- d7b0ab9462ea8d51fffd55e69f1d0a036d4cfaa224349cd317bef2d32b23bb0ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40690
the chainentry 40690
- sealed to the entry before
- b6caf17165474334aff9a12ef67fe16ff01a650f50d9a8348128408c1c5a1aec
- this leaf
- 7ef90a652bdd2ec1fb66dab1d8b4f6b39260b08f7ad9293f00b23e0fa98b90c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zDNY9195PVswNeySZymrTfjMqRGzrgMxJ1uZPffx9K83vuQKpiVZeubbB7SzY9KUpQsZb82qaw9/HsaG15sdCw==