1.3 Payments & Transfers

This release introduces key features and enhancements across user experience, security and performance.

User Experience & Performance Improvements

• Save and Use Drafts: API is enhanced to save drafts with Pay Later and Recurring options.
• Share Payment Confirmation: Payment confirmation can now be shared using Payment confirmation API.
• Payee Management Access Control: API for access control is enhanced so that Account, DD, and P2P tabs can now be hidden from Payee Management transaction if a user lacks access to respective payees.
• Enhanced Payee Image Handling: Payee Image API is enhanced so that Payee images will now be automatically resized when uploaded.
• Display Bank Code in Recent Payments: Recent payment widget/inquiry API for both incoming and outgoing transactions are enhanced to display the bank code for better identification of the sender/receiver bank.
• Enable 'Refresh' on Outward Payment Inquiry Page: The Transaction details API is enhanced to allows refresh only for few relevant statuses.
• Payment Networks & Purpose Codes: API is enhanced for Payment networks so that it can now be fetched from the underlying Product processors for proper mapping with purpose codes. Bank user can map the desired purpose code to the network and same will be available on the payment screen.
• Account API Enhancements: Account API is enhanced to now supports configurable parameters for Search-As-You-Type and Search Filter by Criteria.
• E-Receipt Download Option: Payment API is enhanced for Retail users to now download e-receipts from the confirmation page.
• Optimized API Calls for Payments & DD Screens: Unnecessary API calls have been removed, improving performance and reducing system overhead.
• Migrate Favourites to v2 API: Favourites have been successfully migrated to the latest API version.

Cross-Border Payment configuration

• Payments API is enhanced for Cross-Border Payments as it is now configurable, enabling banks to customize it according to their specific requirements. This ensures that users see only the relevant payment fields as configured by the bank. Implementation partners can configure cross-border payment transactions to meet bank requirements without the need for code changes.