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
- ef9c8b988eda9e8859161fe74eaae9bcc405b03cb2c35eac8159dd225570b7a2
- request
- dedac8941c449789ba6f7010cca4800a3f5de0bc4300af6405d2e8eed97668b3
- transaction
- 4f138a48447ec79d22fe17ab082abddc627bb0226d776128b1260457a453fb04computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64850
the chainentry 64850
- sealed to the entry before
- c866fcf4aafdbad4b4c13bb1f5ceed7cda462d1bb48c80c4719488b207b340f8
- this leaf
- c153f27665e03155e43c4f8fc99e1bf07045cb1782ec0b8339843dcfec4a7363
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TCJFbYq8F7AObO//xrNwgjdHh6EtQGGb6dIHmAA2uTzc5SLUm9nol9A9VMnpdy6wq2Oao6IdLJAHnDesJATmBQ==