What's new in API v 1.3: main changes
Update to the newest version:
Praxis is a company that always strives to provide its customers with the best online experience. That is why we create long-lasting relationships with merchants. We do that by providing the best integration solutions for online payments.
In order to provide you with the best user experience possible, we sometimes have to upgrade our API to support newly added functionality. We recommend that customers re-evaluate their integration from time to time - at least once a year - in order to take full advantage of the new features.
On this page, we outline the main differences and changes that are part of API v1.3. Please review them before you plan your migration.
Differences of API 1.3 to compare with previous version
1. Enhanced security:
- Different improved approach to authentication;
- Possibility to send credit card details in an encrypted format.
2. Different data structure (objects). Each object contains details regarding one of the parts of communication - Customer, Session, Transaction, etc. Integration with this approach is more efficient and allows more extensibility for the future.
3. Extended data in notifications. The ability to pass more information received from PSP in the CRM callback i.e. account number, IBAN, system settings etc. We could also use extended notification to relay information about configuration such as Fees applied.
4. Tokenization for cards and e-wallets. In API v1.3 introduced the customer_token, card_token, wallet_token. A token is a way to refer to stored details without having to repeatedly collect and send the full customer, card or wallet details over API. Some merchants use this functionality to pre-authorize a small amount from the end customers credit cards. The credit card details can then be safely stored in our PCI environment and the merchant get back a token that corresponds to this authorized credit card. From that point forward, the merchant can send the token in place of the actual card.
5. New API method to retrieve an information regarding all available gateways and its' parameters {get-gateway-options}
6. General flexibility is higher than in previous versions.
7. Javascript SDK is a toolbox to help the merchants initialize, position and control the cashier container, tab or window.
8. Transaction Verification. It is an advanced feature of manual transaction update that automatically detects discrepancies in notifications we receive from PSPs. It also avoids false updates to the CRM. Certain cases require additional approval before the amount is credited to the CRM. This can be done by reviewing the PSP's dashboard. This is because there may be 2 notifications and we require the additional manual verification to resolve the conflicting statuses.
Summary of the differences
If you are now on API v1.1 - please check this summary of what is new in API v1.3 here
If you are now on API v1.2 - please check this summary of what is new in API v1.3 here