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
- ba3dbf9b00c316dfdd1a34e3bcada00b1f69cb0de8fd990334ce55b604c7c8a3
- request
- a635b67c5bc2455a51869826ba256c39aff66582f65a862db099f258d7f93074
- transaction
- 5f53d73eadabae9ce23ebac38b8183977a225438d6482feb871b95b7acac51f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21574
the chainentry 21574
- sealed to the entry before
- 853aba7d7782a582654f9d79f539da5aefccdb1dd0c5565d1fa720b1cab04376
- this leaf
- 2700bd56584aaa9e682ae6b34455d65becd428582dba7a4ce80e2789b98f21e7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v4QBoWxjdbwa3cl1id8Rw99bN4sloG+UNToteAPRhEGJZuwc9x9G7KxZr5sUFsm34rn21AkJA1sz13W+7n7kAA==