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
- 918a1ed8fa541dce35c48a1d7e8616ea10de3f66ed50909b20823e6e0e61ea8c
- request
- 6f75203a2339256d1298c38bc29e83302eb1a2b7ba220db098917558a4844a8f
- transaction
- 51eea85adaf87565f74780e39229c3630716de4327c900ab24bd30f9d4675a62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22047
the chainentry 22047
- sealed to the entry before
- 59994282af451618d7e14c976d4fb2e23915079e3e52b9bab51913ee87ba769e
- this leaf
- 4b9660c99a107ebc14c99afa83728b8a0014c2ba02f4f0b3099c4cf3c2560ef1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2GcbOi8ctnhvOm965/DaRrzOHEEbYpN6sKET5Jdh/h8uMGl77Fuerwe8NdrVgoUQMA3+IiJnSep+3Zg3L5tODA==