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
- 4e3a9d642be60614f712bd13874150a619bbf885868eae6d9add7b17710b9653
- request
- d6412d675a61afe971a3b22b268aac892f785d1f24207bced303d9e9a8539cc8
- transaction
- 5378375baa000d2d9914216a394b3ff3da7071016a9b70661b5ee89558eac137computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42106
the chainentry 42106
- sealed to the entry before
- cb796f28825d47742e43ff10cf13985a765a81b1c4924d44ccefe3de2af96f98
- this leaf
- c9b56d6e053b66e57278c4ac4ef1e459893f442cd7d02c931db8df540e51d354
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ThcARE42ESJKJycGW+wd9gBhqcNy9mYB8945+f/puqGz/km0JNbWJ+8vQ4lY9sYSuBbYnpnbAFORj09dRpBEAg==