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
- da8363331d2d686eb5290dd4cfd6fb2d2d0a5e4d4d6d49e430e72ac8671015fd
- request
- dea11c203579db040cd3f1c61f33c9ca903c4f203513964ec7876f02bfefed8f
- transaction
- 1a649ae0276050647b99625ce4b7cc977a9a9703876f19e746a5e8b4f1550bb5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32959
the chainentry 32959
- sealed to the entry before
- 3defbfa67ca1c013d6cd5fe4de23a96afa17c4bf0ac1e9001465eb8b7bc845e9
- this leaf
- 128afd6102245c28a38d3e57763d26a3abb883706309a3d3e90ba675cc8ae582
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iViRg7sKgxfc9Fbu6Zz8l9Gg5gsnz+WNZfOZu0r5Jkan8c8UyRN5kx9gK2n+L8nLVadY7k6CuQzKbVuBz38yAg==