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
- 7e09903617b6fa9531975a9db17b739e73035094a211a48fab26b793b00be2c8
- request
- f3c538df27f32347958b10ef25bf69922fa4b5755c47cc3727fda7abd56b21a7
- transaction
- 2ffa9b71aabac566d10b69bb78cb067287e2a9652ff020fde0aa7dd5d3d39699computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69305
the chainentry 69305
- sealed to the entry before
- 5fc9aa21c089bbd23337b77bcbcf913a6d10e832e013d704ae44f934fd2a2174
- this leaf
- 76cfd62ef2f91e023aee521d525c3f78ab6d5a8c9ec15cce96e59b2795f26e3b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kOq9doKzD+dqpsjRCTtEH+NiqBWHWWPf/q6R0wMM+oCF8D8R05EXJPx4hCh1KFoOJ3xHnozAo0fFMK02le8hDg==