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
- f9071c7c5666bd783e2add042c5d166e013f72241b584c73f26558b2b61d0f49
- request
- bb28c95892b23361ba9a569a4ba2928c69d8855ed87272f7f17ac3fa57a44472
- transaction
- b36caf236cc98124d55ba11c841c06c133351225a671a6d9db4cd3e10fde5bb9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46174
the chainentry 46174
- sealed to the entry before
- 4eb3f65f259a309aef45b6efc5298968556d1480bea8dda7a02cbb8949996507
- this leaf
- 4e20f722d16e4f4b8c1476f5463510ff5eaf75e349ab1cd89c587bc68c439c4e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EPh0J0B9WRZmEFXIa60jZ2FS8EFTntJIvsowPZD4G2AGzasJ0T4dQAm19o3EcfttygqMj2O8oA1+JBeksTOTDw==