If you want to create a campaign you can find more information in this link:
If you want to open a free trial account you can find more information in:
If you want to import contacts you can find more information in this link:
If you want to create a target you can find more information in this link:
If you want to duplicate a campaign you can find more information in this link:
If you want to review your campaign you can find more information in this link:
Unicode standard is a type of character encoding system designed for consistency in the computing industry. The unicode system is able to handle large variety of characters beyond the basic Latin alphabet (A-Z), in order to support a wide range of languages and technical symbols.
If you want to buy credit you can find more information in this link:
If you don’t remember you password, you can find more info in this link:
If you want to deactivate your account you can find more information in this link:
A unicode message is a message that is encoded using the Unicode standard. Any message that contains even a single Unicode character must be encoded in this way in order to display properly the Unicode characters properly.
A single Unicode character requires more space (2 bytes) compared to standard GSM encoded characters (1 byte). As a result, the total length of a Unicode message is shorter than a message with standard encoding. A Unicode message can contain up to 70 characters before it must be split into multiple parts.
The limitations for multi-part messages are a little different: a single SMS in a multi-part Unicode message can hold up to 67 characters. The three characters are used up by the information that mobile phones then use to join message parts together in the correct order.
If a message displays in your Outgoing SMS Report as Sent, this means the message has been delivered to the carriers by PUSHTech™, and PUSHTech™ is awaiting confirmation of message delivery from the relevant operator. In other words, the message has been sent out successfully, and PUSHTech™ is waiting on the relevant carrier to relay back that the message has been delivered.
By using Unicode, PUSHTech™ is able to support any written text that is part of the Unicode character set. This include an extremely comprehensive list of scripts from around the world. Please note that for a message to display, the destination handset you are sending to must also support the Unicode characters you have included. If you would like to read more information on Unicode, please refer to the article What is a Unicode Message?
PUSHTech™ Chat module is like SMS, but more powerful. You can send messages, photos, videos and documents to people who are in your phone contacts (and have PUSHTech™ Chat module integrated). You can also create groups for up to 200 people.
PUSHTech™ Chat is currently available for iPhones (iOS 5 and above) and Androids (2.2 and up). We support tablets and smartphones alike, as well as iPods.
We also have a public API for developers, should you want to build your own applications for other platforms. In the meantime, get your best friends to switch back to iPhones and Androids.
By default PUSHTech™ Multi-Factor Authentication blocks an attempt to initiate another PUSHTech™ Multi-Factor Authentication request for the same number while there is already one ongoing – therefore, DO NOT implement a Retry button with another PUSHTech™ Multi-Factor Authentication call – this would be rejected outright.
Retries should be implemented with two subsequent calls:
1) Cancel the outstanding verification request
2) Issue a new verification request.
Please use our PUSHTech™ Multi-Factor Authentication Control API to cancel an outstanding verification request.
Yes. Developers for all platforms are welcome to use our API
One tick — message sent (and is on our server, waiting for your friend to open PUSHTech Chat), notification sent (your friend is notified, if he receives notifications).
Two ticks — message read (your friend opened PUSHTech Chat and opened the conversation that had the message).
PUSHTech™ Chat is more secure than mass market messengers like WhatsApp and Line. We are based on the own protocol, built by our specialists, employing time-tested algorithms, to make security compatible with high speed delivery and reliability. We are continuously working with the community to improve the security of our protocol and clients.
PUSHTech™ Multi-Factor Authentication enables you to verify whether a phone number is valid, working and whether your end user has access to it (hence it is likely she is the owner). Verifying phone numbers is a mission-critical process and is typically used for :
Protection from SPAM – «Are you a real person ?» : by verifying phone numbers you are in effect preventing spammers of mass-creating
Protection from hacks – «Are you who you say you are ?» : if you detect suspicious (password reset, logins in a new location) or significant (request for a service upgrade) activities, you can challenge whether the person initiating these is the genuine user whose number is linked to this account
Reach Users – «What is the best way to reach you ?» : ensure you have the right number on file so that you can get in touch with your customers when you need to
Example of use cases :
Challenge following Suspicious activity
Refresh user details
Reactivate inactive users
When it comes to secret chats, you don‘t — just make sure that the visualized key of your secret chat matches the one in your friend’s secret chat settings.
There are simply three API calls :
- Verification Request : provide the number to be verified and PUSHTech™ will send back a Verification Request ID for future reference. Some requests might be rejected outright (e.g. invalid numbers or parameters).
- Verification Check : provide the PIN code obtained from your end user along with the Request ID in order to know whether it matches the PIN code PUSHTech™ Multi-Factor Authentication sent to the end user.
- Verification Search : look up one or multiple requests in order to know their status (In progress, Successful, Failed or Expired) and many other attributes.
Check our complete API docs at https://developers.pushech.com/api
Yes, PUSHTech™ Multi-Factor Authentication works with both fixed and mobile numbers in all countries around the world.
PUSHTech™ Multi-Factor Authentication has a unique charging model called «Pay Per Conversion» :
You only pay for successful verifications (i.e. the PIN code you gave us matches the one returned by the end user)
You do not pay for unsuccessful attempts (ie SMS we sent, attempted TTS calls or even completed TTS calls that resulted in no successful verification)
We offer «Pay Per Conversion» to our customers and we are confident in our ability to make it work, but also believe we all benefit when our interests are fully aligned with yours. However please note we also ask you to not abuse this feature by following a few simple guidelines :
Use PUSHTech™ as your primary if not exclusive Verification vendor
Ensure your application clearly explains to users that a verification will take place e.g. require their consent for it to start by placing a button.
Once the user has acknowledged they want to start the verification, display a screen where they can enter the PIN code
No, you only pay for each Verification request you make to us which results in a successful verification. You do not originate the SMS and TTS retries : we do. For each successful verification request you pay the same price regardless of the number of retries we made.
The total time is influenced by a variety of factors including some related to the usability of your service/app/website. We expected the process to take from less than 30 seconds in most cases to at very most 10 minutes in extreme cases where numerous attempts are done via primarily TTS calls.
MFA - Why is my PUSHTech™ MFA TTS call not placed in the primary language of my destination country+-
If unspecified with the request, the product (upon determining the country for the verification) identifies all the languages spoken in the region and picks up the most appropriate language available. In this case, Polish is one of the most widely spoken languages in Ukraine, next only to Ukrainian. Because we do not have Ukrainian Text-To-Speech, the next best match available is Polish and we fall back to that. Unfortunately, the best way to handle this would be to specify a locale with your request.
Yes you can verify most fixed line numbers around the world except :
- Premium numbers
- Toll-free numbers
- VoIP Numbers (ie virtual numbers such as Skype Numbers)
When you try to verify one of these numbers, we will reject the verification request and no SMS/Call will be made.
Countries where PUSHTech™ Multi-Factor Authentication is not supported by default – (contact support@pushtech,com if you need these restrictions to be lifted) :
Antigua and Barbuda
Heard Island and McDonald Islands
Papua New Guinea
Republic Of The Congo
Saint Pierre and Miquelon
Sao Tome and Principe
United States Minor Outlying Islands
Wallis and Futuna
PUSHTech™ Multi-Factor Authentication enables you to verify whether one of your end users has access to a specific phone number by challenging them with a PIN code to enter into your application or website. That PIN code is sent by PUSHTech™ via SMS and/or TTS (Text To Speech call).
PUSHTech Multi-Factor Authentication hides all the complexity and takes care of :
- Delivering verification messages and calls
- Failover management using the optimal workflow (sequence and timing of attempts) across Voice (Text To Speech – TTS) and SMS
- PIN generation and expiry handling
- Template management : localized in 23 languages for SMS and TTS and optimized depending on the delivery metho
- Simple pay per conversion and pricing
Of course you could choose to use our SMS and TTS API’s instead but you would have to build, maintain and manage the above capabilities by yourself.
PUSHTech™ Multi-Factor Authentication generates ‘Time-Based One-Time’ PIN codes according to RFC 6238
- PIN default length is 4 digits and can be set per API call to 6
- PIN expiry time is 5 minutes
If a PIN code expires during a workflow in progress, a new PIN will be generated for this verification request for the next attempt. This means that the old PIN is no longer valid. Hence any future verification checks for this request will need to use the new PIN.
When you submit a verification request you receive a request ID that you need to provide during the Verification check alongside with the PIN Code from the end user.