Help & Support Register Login
AA

New Payment Process for Requests:
We have shifted to a new payment process which accepts bank transfer or credit cards via Western Union and will no longer be accepting payments sent through to Connecting Up. For the updated instructions on how to process payments, kindly click here.

Validation Services

Having a hard time wrapping your head around what the Validation token is and how to sort out issues related to it? See all the answers you're going to need here:

 

What is a validation token?

A validation token is a unique code that a person uses on behalf of an NGO that has been validated by TechSoup Asia. The token is used to access products and services intended for NGOs.

Once a validation token is successfully used, the NGO is considered valid by the provider of the service or product for the time period applicable to that program.

Learn more in this instructional video:

 

What does a validation token look like?

A validation token looks something like 123a4567@MyNGOname

 

How do I get a validation token?

Validation tokens can only be created by the TechSoup Asia account holder and only issued to someone who is authorized to represent the NGO. Because validation tokens expire after 60 days, it is best to create them only when they are needed.

 

If you are the TechSoup Asia account holder in your organization:

  • Log in  to your TechSoup Asia account account.
  • On your My Account page, go to the tab called Validation Token.
  • Click Add a new token.
  • Enter the first name, last name, and email address of the person who will be using this validation token.

    • Important! This must be a person who is authorized to represent your NGO. For example, it could be a staff member, a volunteer, a board member, or a consultant acting with the full knowledge of your NGO. Do not create a validation token for someone who is not authorized to act on your NGO’s behalf.

  • Click Add new token. Your new validation token appears.

  • If you created the validation token for your own use:

    • Copy the validation token.

    • Paste the validation token where it was originally requested. 

  • If you created the validation token for an authorized representative of your NGO to use:

    • Copy the validation token.

    • Paste it into an email to the authorized representative.
    • The authorized representative then pastes the validation token where it was originally requested.
  • If you are not the TechSoup Asia account holder in your organization:

    • You will need to contact the TecgSoup Asia account holder and ask them to create a validation token for you.

    • A validation token will only be created for you if you are authorized to act on behalf of the NGO
  • If your NGO has not yet been validated by TechSoup Asia:

    • You will first need to go through the registration process. 

    • Once your NGO has been validated and confirmed as meeting the required criteria, you will be able to create a validation token by following the steps outlined above.​​

 

What do I do once I have a validation token?

  • To access services or products designed for NGOs, companies or retailers that work with TechSoup Asia will ask you to provide a validation token to prove your NGO’s validity.
  • Copy the token from your TechSoup Asia account and paste it where the token is requested.

 

How often will I need to use a validation token?

  • To access services or products, you will only have to use the validation token once.

  • You may use that token for offers from other providers as well, until the token expires.

 

When will my validation token expire?

  • Each validation token has a life span of 60 days.

  • Because validation tokens expire after 60 days, it is best to create them only when they are needed. 

  • Expiration of your token does not affect your existing services. For example, if you use a token to access and afterward that token expires, your established validation for the service will not be affected.

 

What do I do if a validation token expires before it is used?

  • The TechSoup Asia account holder can update a validation token that has expired.

  • Updating an expired validation token replaces the existing code with a new code and sets a new 60-day expiration date.
  • If you are the TechSoup Asia account holder:​

    • Log in to your TechSoup Asia account.

    • On your My Account page, go to the tab called Validation Token.

    • Find the expired validation token in the list presented to you (the name and email address of the person you originally created the token for appears alongside it).

    • Click Update Token. The validation token is automatically updated.

    • If you updated the validation token for your own use:

      • Copy the validation token.

      • Paste the validation token where it was originally requested,
    • If you updated the validation token for an authorized representative of your NGO to use:

      • Copy the validation token.

      • Paste it into an email to the authorized representative.

      • The authorized representative then pastes the validation token where it was originally requested.
    • If you are not the TechSoup Asia account holder, contact the TechSoup Asia account holder and ask them to update the validation token for you.

 

How many validation tokens can I have?

You can have unlimited validation tokens, provided you are authorized to act on behalf of the NGO.

 

Why would I want a new validation token?

  • The TechSoup Asia account holder can update an expired validation token or create a new one, at his or her own discretion.

  • For example, the account holder may choose to create a new validation token, rather than update an existing one, if the new token will be used to apply for a different product or service.

 

Can several people in my NGO each have validation tokens?

  • Yes. Validation tokens can be created for anyone who is authorized to act on behalf of an NGO when they need to access a product or service that requires a token.

  • Because validation tokens expire after 60 days, it is best to create them only when they are needed.