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
- 64b386c90070c367d4bd55029bccc64307355f233c5522901c61f9af16dbf4a7
- request
- 8a59b66e19b7427d0560c6ddad5c9c94d94fa0c6afd725110f156e10836b5057
- transaction
- d96868034493169e1bdef744ac2eb56d3e92a58d88a1f50f0183e4253d1598b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62726
the chainentry 62726
- sealed to the entry before
- 7c8d445b674ce1598ca82f51095c3190ad9b98facc29f6dbbb8bbb856ca3957e
- this leaf
- 847148828f9c2e972fd94d1a763fe670931217bd67847a54c7d758e7f3b80ef9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BMjphpqeLKxZ/1RPsLx73pviXDcY9HR892r0nywMj0/RNsMfRPYLBifvBExgD5Tr1FAQGf5KgaWBuvQWYAzeDg==