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
- 2e6e13f03cb9084541c04269d868943c95e68d3d669439b352341c2433efbc6f
- request
- 6166b8f27a4712d89722a8e5ec50c4486c287a4b05e1c993268b188697444766
- transaction
- 393a371c04d2e6c51dfbbb17850b5d77387d44f0831c47fe4e569ebcc4d81592computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77030
the chainentry 77030
- sealed to the entry before
- a6232f21fa22fdff79db8521b905693d3e89fdc133c364f3d966a44e0bbd6031
- this leaf
- c21fb5e776e542870ff34bc909ff042f33e4ce5269a07533f1add7b52b01dd84
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4NoHPDOR4UYobvcDg1dVB7xFryc4gCiAGR7cCLYkKt+VySiUi3IRjo8Rj8FbUdFWWrfp1nfQiH3I1g1Z3k2aBQ==