Resolve Xero customer conflicts - Currently, when Xero transmits a customer name that doesn't conform to the required naming conventions, Pay Advantage automatically adjusts the name to align with the correct format in Xero. However, if a new invoice arrives through the same mechanism that prompted the initial renaming, Pay Advantage will rename the previous customer import by appending a "2" to their name, while also creating a new customer for the incoming invoice. To streamline this process and prevent duplicated customer names in both Xero and Pay Advantage, we're introducing a new capability. This feature ensures that synchronization with Xero won't occur until the customer name is correctly aligned in both systems. While this approach safeguards against naming discrepancies, it does require manual intervention to address any naming issues. To start using this feature, in your Xero settings dashboard change the setting of Xero synchronisation issues to off.
Store a Credit Card in Pay Advantage without Charging - The credit card creation API has been enhanced to offer more flexibility. You can now include a flag when calling the API to specify whether you want to validate the card or not. Opting for no validation means that if the card is found to be invalid when a customer is charged at a later date, the transaction will fail. On the other hand, if you choose to validate the card, please note that authorization fees may be applied. This feature allows you to tailor your payment processing to your specific needs, ensuring a smooth and secure transaction experience. This is found using the /payment_authorizations endpoint with the validate_card parameter set to false.
NEW API Portal Thehttps://docs.payadvantage.com.au/is a new portal for exploring our Pay Advantage API's. Using the portal enables you to build out the API call with the required parameters. If you authenticate and add the bearer token to each requests, the API calls can be made directly from the portal.
Webhook Status Updates - We've expanded our webhook support to include DDR (Direct Debit Request) creation and processing, offering webhooks for each event within the DDR lifecycle. This means webhooks are now generated for payment creation and any failures that occur during batch and DDR processing. In addition, a new webhook status, the payment "settled" webhook, has been introduced. This status is essential for tracking payments, particularly in the context of DDR payments via bank accounts, which typically take three days to settle after creation. This webhook is triggered once a payment is officially settled, providing crucial confirmation of its acceptance. During the intervening period, where payments can still fail, you'll also receive a "failed" payments webhook to promptly address any issues. These enhancements ensure you have real-time visibility and control over your payment processes. For further information refer to our new API portal
Comments
0 comments
Please sign in to leave a comment.