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
- 97adf196482bc22e444f18eec40306e309a5033d9075dd76eac12094e160d795
- request
- 2e1f53435afef784b5c7575ed8f584b52a86a5907c3c1be7f9f4d2f4f5d8cf0f
- transaction
- a46ca6bac619c84df9d16b5daf13ff22c0b14f9d4c812d71ab4af7f26f7cc99dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75925
the chainentry 75925
- sealed to the entry before
- 9402c69b01c211059ad7e4c35797aac2cf6e7e464626f4af554cc1b3ccb65650
- this leaf
- c6c6449af5344b094fd33d05b84b6edd0fd08cd014b42d13567fcc381b4c2a4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gid0p8k45lws/rjEuvGMrpZRfzhzG19UBePPjnc+JRqFSuoc+qKd2guVHeMYa0LNx7dY0T8dtZdOCdpl3JKnCA==