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
- b0298b54b8caf330c7afe5917d413b59786bb6c4051f756079fe8b134ff68b04
- request
- 045b7d3e8e74468255249769e59087543f9c49465f216bf8017faed7043c95ae
- transaction
- c04833fcf33439a2f92c7d264e6e3ada090da15468775d390606db9bf7c48e74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33920
the chainentry 33920
- sealed to the entry before
- fd7cea5dea7c06254f1bfd5cb2ca555e5d3bca62cbc3752ee63e99a82adf2d30
- this leaf
- 2d535962e6ece13959872509dd8d821b9e67c34e3efc940b5d43f825fdbb0ef2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lSRzYTiNtXNT/cbjzLTvM+l3yNCfMl7tkgi+l5vZBd2UgPGPRzm2sUcnpIB3HegRbabWfhLAUuzCugBQcaqvBw==