1. What is Linkly POS accreditation?
POS (Point of Sale) Accreditation is the certification process that ensures a POS software solution is compliant, secure, and compatible with Linkly’s payment gateway. The accreditation process verifies that the POS system:
- Meets functional and security standards required for processing payments.
- Works seamlessly with Linkly APIs
- Handles transactions accurately, including edge cases and failure scenarios.
- Is stable and reliable before being used in a live environment.
Once accredited, the POS software is officially listed on the Linkly website, confirming to banks/acquirers, and merchants that it meets the minimum integration requirements and is approved for payment processing.
2. Is there a cost for POS accreditation?
No. Integration and accreditation support is provided at no cost.
3. Who do we contact for support during POS integration?
Contact Linkly’s POS integrations team via POSIntegrations@Linkly.com.au.
4. What information is required to get support?
- POS name
- Company name
- Key contact details
- Integration type (OnPrem / Cloud / MPOS)
- POS hardware OS
- Details about the request/error, including screenshots, API requests and responses.
- Itemised list of events to reproduce the error.
- Attach logs if applicable.
5. How do we get accredited?
When you are ready to accredit, you will need to sign up to access our Accreditation Portal a and complete the form, online.
Kindly review the test cases for your chosen integration type and complete all test cases and submit the following under Actual Result:
- TxnRef used for the transaction.
- Date and Time of the transaction.
- EFTPOS.log file (For OnPrem integrations).
- Full API request and response. (For Cloud and MPOS integrations)
Screenshots of the POS application and receipts, if applicable.
6. When does the POS Vendor submit for accreditation?
A POS vendor submits for accreditation after completing development and internal testing to ensure the solution is ready for review. The key milestones before submission are:
-
Initial Development & Setup
- Access API resources and documentation from Linkly.
- Validate the installation using Linkly’s Test Harness.
-
Proof of Concept (POC) & Full Solution Build
- Develop a Proof of Concept (POC) to test API interactions.
- Expand the POC into a fully functional solution with all required features.
-
Test Case Development & Internal Validation
- Write test scripts, including edge cases, merchant use cases and disaster recovery methods.
- Fix errors and complete all internal validation.
-
Accreditation Submission
- Login to the Linkly Accreditation Portal.
- Select the relevant integration type and submit all required data for the test cases, including logs, API requests/responses and screenshots of the POS application where applicable.
7. What test category do I choose for my Integration?
Please select “OnPrem and Cloud API v1” for both OnPrem and Cloud integrations. For MPOS integration, choose “MPOS”.
8. Which integration types require log file submission?
Log file submission is required for Linkly OnPrem. Logs are submitted via Linkly’s portal or email as specified during accreditation.
9. Some of the mandatory test cases do not apply to us, can we skip them?
If a test case is not relevant to your integration, you can request an exemption from Linkly during the accreditation process. The POS vendor will need to provide a disclaimer against the test case.
10. The Power Failure and Get Last Transaction test cases do not apply to our integration, can we skip them?
No. These are mandatory for all POS integration types and cannot be skipped.
11. Can we edit/update the current submission?
If the details on your current submission are incorrect or need to be changed, you will need to delete the submission and re-submit a new accreditation script.
12. What if we want to accredit for additional features in future?
If the POS software is already accredited for Core Payments (Purchases, Refunds, and Error Recovery) and you want to add new features such as Surcharging, Tipping, Cash Out, etc., please submit a new accreditation script to accredit for those additional features. You will not need to redo the Core payments test cases.
13. What happens if my accreditation submission is rejected?
It is generally not rejected. Linkly provides feedback on missing or incorrect test cases. The vendor must fix issues and resubmit the accreditation request. The review process restarts, but previous submissions may speed up re-evaluation.
14. What happens after accreditation submission?
Once the accreditation is submitted, the following steps take place:
- Linkly Review & Feedback:
- Linkly team reviews the submission, ensuring all test cases are completed.
- If issues are found, feedback is provided, and the vendor must fix and resubmit.
- Approval & Listing on Linkly’s Website:
- Once approved, the POS software is officially accredited.
- The POS software details are listed on Linkly’s website, making the accreditation visible to our partner acquirers and merchants.
15. How long does the accreditation process take?
It depends on:
- The complexity of the POS integration.
- The completeness of the submitted test cases and logs.
- The number of review cycles required for approval.
On average, it takes about 5 -10 business days.
16. Can I make changes to my POS software after accreditation?
- Minor updates (e.g., UI changes, minor bug fixes) usually don’t require re-accreditation.
- Major updates (e.g., new payment methods, API changes) may require full re-accreditation.
17. Does accreditation expire?
Accreditation does not expire under normal circumstances. However, vendors may need re-accreditation if:
- They make major updates to the POS software.
- Linkly introduces new API requirements or security updates.
- The integration method changes (e.g., switching from on-premise to cloud, MPOS).