Pay Advantage 8.15
DDR payment API uplift
Payment to DDR query
We've simplified the process of associating a DDR with a payment. With the newly introduced feature enabling search by ddr.code in the GET /payments endpoint and the inclusion of ddr.code within the payment record itself, linking payments to specific DDRs has become effortless. Now, you can seamlessly identify which payments correspond to which DDRs, streamlining your workflow.
Search payments using DDR Code
curl --request GET --url
'https://api.test.payadvantage.com.au/v3/payments?ddr.code=AAAAAA'
--header 'accept: application/json'
DDR Code available on the payment record
{
"Records": [
{
"Code": "ABC123",
"DateCreated": "2023-12-07",
"DateFailed": null,
"DateClears": "2023-12-12",
"DateSettled": "2023-12-12",
"DateUpdated": "2023-12-12",
"ReadyToSettle": true,
"FailCode": null,
"FailReason": null,
"PaymentType": "realtime_credit_card",
"Amount": 200,
"AmountIncFees": 205,
"AmountRefunded": 3,
"DDR": {
"Code": "AAAAAA"
},
"Customer": {
"Code": "ABC123",
"Name": "Bob Smith"
},
"BPAYReference": "123456789",
"ExternalID": "Your External ID",
"SettlementCode": "AABB12"
}
],
"Meta": {
"page": 1,
"recs_per_page": 1,
"total_recs": 1
}
}
Webhook Data payloads
Previously, our webhook implementation required API users to make subsequent calls to the Pay Advantage API to obtain additional data about the received webhook. However, we've improved this experience by directly providing the payload that would typically be acquired through such API calls. This enhancement significantly reduces the need for extensive developer coding and enables immediate action upon receiving the webhook.
If you prefer not to include the webhook payload data in your webhook, we can ensure that you are excluded from the latest webhook update.
Example payload:
For information on the full release visit: https://help.payadvantage.com.au/hc/en-us/articles/9351555245839-Pay-Advantage-8-15-0