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
- 26b4158b0c10eb9a00198f1085ee99f0bd45bb7dd578ed3184fe899c5a5f8699
- request
- 309a821e2a8bcad64587a550ab706b53fc8ed8d165ff45e2581148edfa9496f9
- transaction
- 5daa959106d479ee0b87f24a6b38ff0e7382e13af07e710055ffc77955ca029ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40105
the chainentry 40105
- sealed to the entry before
- 106fd26d9cc6e53b0a1d550b2f19b1ddf9a0e3bea8ac7cd3169fba3a268cea41
- this leaf
- 31aa34e748ca26244b35a7112128faf3a1b794a13fe41c3fee26ccb1bda487fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u0WGiTI1cBt+qoQsPa1F+7Q1uJlsIpdfA9eCoTbiaiydTFUYkgLVJPmQNac8DNuWddgVvO9q5VQHgHaM3LcSBA==