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
- 2d6a8b47d6127b484a1ac31f52ac0a555e26ba1102c84d545913775926860733
- request
- aefaafb70a94725382acda8929dc785b879e4686696b6ff2e21546e129c6e908
- transaction
- 42bc5682e5bf86da70b0bc26b2e23edf78b06b4021ec5d478fe5fc8b5fd34590computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28550
the chainentry 28550
- sealed to the entry before
- 0e7f8c55ce8c2c03874118c6c61da260327e1f1422547e1ca2c0f02ab39a9097
- this leaf
- 38f145370d453205fc836297ec03b996ae9937447e950726f0b67411432ca946
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- txcu+DTBmNrNSt3ZhXwZced56bZMZUwYJ747C7hes3JN3h+7J58uznDo73vawrXf8NpY040HpBIfvXZSBc3XAg==