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
- 73af5d9eb1610950d348407a372bd6bbcae5b3e0d9d9bfc939f00cb74d3440b6
- request
- 6d995821c633bf553efc7b93eb9167eccb51c7dadc94b90e7802f8c3a2f0427f
- transaction
- bde28d89e626ed5f16f2957a96f57522a7fbba5d88031ba39d6d3d7ed537c3aacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70264
the chainentry 70264
- sealed to the entry before
- 233a87385df9233d31a2142f65f7df6421d5b7d5d387e3de002fcbd1bc9bac0a
- this leaf
- 9d64d88eed5c8eeb6bfa6bdaf73981da505ead46d33bbacca95355528e8ed4b8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- o9EY4rcYCixsKZX+gNiGeYBjQFzg9yKmmLzm3uXRmGufUVDASsxgHPbKtDVQZFCs5f/jZ/TjbPk3YyeWbWTKDA==