Telecommunications (Service Provider — Identity Checks for Prepaid Mobile Carriage Services) Determination 2017

The instrument builds from a small set of operational concepts that determine what must be collected, how identity is verified, and how records are treated. The principal concepts in the text are:

• Customer types: The instrument distinguishes between a purchaser and a service activator. Table 2 sets out different items of information to be obtained from a purchaser (for example, name, residential address where not acting for an entity, and the number of other activated prepaid services supplied to the purchaser) and from a service activator (for example, name, date of birth, residential address where not acting for an entity) (Table 2).

• Activation count trigger: A core threshold in the purchaser-verification rules is whether the activation "will result in the purchaser having 5 or more activated prepaid mobile carriage services". Different verification standards apply depending on whether the activation pushes the purchaser to five or more active services (Table 3).

• Payment-method mitigation: For purchasers, the verification burden is reduced where the purchaser offers to pay by credit card or debit card and the activation does not create five or more activated services. In that circumstance a carriage service provider need not take further steps if the purchaser offers to pay using a credit or debit card (Table 3, item 1, note).

• Documentary categories and counts: Verification for purchasers is specified in terms of category A and category B documents, and in the number and combination required depending on the circumstances (Table 3). The instrument requires a provider to "see" the documents and to be satisfied that any expiry date has not passed (s 4.4(3)(a)). A specific handling requirement applies if the category A document is a foreign military ID card, which must be shown at an access-controlled defence site (s 4.4(3)(b)).

• Approved method for service activators: For service activators, the instrument does not set out a list of documents or combinations. Instead, it requires use of an approved method of identity verification specified in column B of Schedule 1 (s 4.5). The text provided does not contain Schedule 1 itself.

• Records and retention period: Providers must keep records sufficient to show compliance for each prepaid mobile carriage service, and must keep the records for as long as the service is activated (s 6.1(1)-(2)).

• Card-linked record requirement: If the purchaser was verified under s 4.4 and the purchase used a credit or debit card, the provider must keep records linking the carriage service number to the credit or debit card used (s 6.2). The instrument gives an example that such a link could be a transaction code rather than storing the card number (s 6.2 note).

• Limits on recording sensitive items: Section 6.4 generally prohibits recording and keeping government document identifying numbers and category A or B documents (s 6.4(1)). There are narrow exceptions where recording is required or authorised by law (s 6.4(2)) and where recording of a government document number is done for a permitted purpose, only for as long as reasonably necessary and destroyed immediately after verification (s 6.4(3)). The instrument also forbids copying or reproducing documents that contain prohibited information (s 6.4(4)).

• Permitted purpose definition: The instrument defines permitted purpose narrowly in s 6.4(5) to include verifying identity of a service activator per s 4.5 and ancillary or incidental purposes to that verification.

These concepts determine the operational design choices a provider must make: which customer role applies, which verification route to follow, what documents to inspect, what to record and retain, and how to handle sensitive identifiers in accordance with the limitations and exceptions in s 6.4.

The obligations in the instrument apply to "carriage service providers" who supply prepaid mobile carriage services. The text itself does not include a definitional provision for "carriage service provider" or "prepaid mobile carriage service". The duties are framed as obligations incumbent on the carriage service provider in relation to each prepaid mobile carriage service supplied (see s 6.1(1)). Practically, the immediate affected parties are:

• Carriage service providers: They are the entity that must obtain prescribed customer information (Table 2), verify identities in the specified manner (s 4.4 for purchasers, s 4.5 for service activators), maintain records (ss 6.1-6.3), and comply with prohibitions and exceptions in relation to recording sensitive identity documents (s 6.4). Carriage service providers also have a procedural obligation to maintain a written description of their compliance arrangements (s 6.3). The instrument therefore places operational, procedural and data-handling responsibilities on providers.

• Customers who are purchasers: When a customer seeks to purchase a prepaid mobile carriage service, they may be required to provide the purchaser-specific items in Table 2, including name, the number of other activated services supplied to the purchaser, and either an entity’s business address where purchasing for an entity or the purchaser’s residential address when not purchasing for an entity (Table 2, Item 1). Purchasers who are close to or will reach five activated services face higher documentary verification thresholds (Table 3, item 2).

• Customers who are service activators: A service activator must present their name and date of birth and, if not acting for an entity, their residential address (Table 2, Item 2). Their identity must be verified using an approved method in Schedule 1 (s 4.5), and the permitted purposes in s 6.4(5) relate directly to verification of service activators.

• Credit card or debit card payers: The instrument singles out transactions paid by credit or debit card in two ways. First, where a purchaser offers to pay by credit or debit card and activation will not lead to five or more activated services, the provider is not required to take any further verification steps (Table 3, item 1, note). Second, where a purchaser was verified under s 4.4 and the purchase used a credit or debit card, the provider must retain a link between the carriage service number and the card used (s 6.2). Those payment-method contingencies affect customers who choose card payment.

• Entities for whom a purchaser or activator acts: The instrument recognises that a purchaser or service activator may be acting on behalf of an entity. Where that is the case, the provider must obtain the name and business address of the entity (Table 2, Items 1 and 2). Providers therefore must gather and retain entity-level identifiers in those situations.

• Systems and personnel carrying out verification and record-keeping: Operational staff or outsourced verification providers who "see" documents and implement approved methods must ensure compliance with the evidence and recording restrictions (s 4.4, s 6.4). The foreign military ID card special rule in s 4.4(3)(b) affects where certain documents can be presented.

The instrument does not itself create direct obligations for third parties such as banks, payment processors, or law enforcement. It does, however, require carriage service providers to link service numbers to payment tokens where applicable (s 6.2), which will imply coordination with payment transaction records.

This section sets out the concrete, source-grounded duties imposed on carriage service providers and the limited rights or permissions the instrument grants.

Key duties

• Obtain prescribed customer information. Carriage service providers must obtain the items set out in Table 2 for each customer of a prepaid mobile carriage service. For a purchaser these include the purchaser’s name; number of other activated prepaid services supplied to the purchaser; name and business address of any entity if the purchaser acts for an entity; or residential address if not acting for an entity (Table 2, Item 1). For a service activator these include the service activator’s name and date of birth, entity name and business address where applicable, or residential address if not acting for an entity (Table 2, Item 2).

• Verify purchasers’ identity under the specified tests. If the customer is a purchaser, the carriage service provider must verify identity in accordance with Table 3 and s 4.4(2)-(3). Two principal paths exist: (a) where activation will not produce five or more active prepaid services and the purchaser is not paying by credit/debit card, the provider must see either one category A document or two different category B documents; (b) where activation will create five or more active prepaid services, the provider must see two different category A documents or one category A document plus two different category B documents (Table 3). The provider must check expiry dates on documents and ensure foreign military ID cards are shown at an access-controlled defence site where applicable (s 4.4(3)).

• Verify service activators using approved method. If the customer is a service activator, the provider must verify identity using an approved method specified in column B of Schedule 1 (s 4.5). The instrument does not reproduce Schedule 1 in the provided text.

• Keep records sufficient to show compliance. Providers must keep records in relation to each prepaid mobile carriage service sufficient to enable compliance with the Determination to be readily ascertained and keep them for as long as the service is activated (s 6.1(1)-(2)).

• Link card transactions to service numbers in certain card-paid purchases. If s 4.4 was complied with for a purchaser and the purchase was made using a credit or debit card, the provider must keep records linking the carriage service number to the card used (s 6.2(1)-(2)). The instrument’s note suggests that a transaction code could serve as the linking record.

• Keep a written description of compliance arrangements. Providers must maintain a written description of the arrangements they have in place to comply with the Determination (s 6.3).

• Avoid prohibited recordings and copies. Subject to narrow exceptions, providers must not record and keep government document identifying numbers or category A or B documents (s 6.4(1)), and must not copy or reproduce documents containing that information (s 6.4(4)).

Permitted rights and narrow exceptions

• Lawful recording or where authorised. The prohibition on recording does not apply where recording and keeping is required or authorised by law (s 6.4(2)). The instrument notes this may interact with obligations under other Commonwealth regimes.

• Permitted temporary recording for specific purposes. Recording of a government document number is permissible where done for a "permitted purpose" (defined in s 6.4(5) to include verifying a service activator under s 4.5) and only for the time reasonably necessary. The controller must destroy the number immediately after verification (s 6.4(3)(1)-(3)). The instrument provides an example where a government online verification service number might be used temporarily to assist a customer who failed online verification (s 6.4(3) example).

• Ancillary records. The permitted purpose includes any other purpose ancillary or incidental to the obligation to verify a service activator (s 6.4(5)(2)).

Operational duties implied by the text

• Check document expiry dates and follow special location requirements for some document types (s 4.4(3)).

• Maintain confidentiality and possibly encryption as per cross-reference to Part 5-1A of the Telecommunications (Interception and Access) Act 1979 in the notes to s 6.4; the instrument explicitly notes that carriage service providers have obligations to keep certain information for specified periods and to ensure confidentiality through encryption and protection against unauthorised access under that Act.

Rights of customers

• The instrument does not specify express rights of customers such as access to records or correction rights. It does, however, place limits on the retention and copying of certain personal documents (s 6.4), which constrains a provider’s ability to retain or reproduce customers’ government document numbers and original identity documents.

In sum, providers must design acquisition and verification processes meeting documentary and method standards, maintain records for as long as services are activated, and enact data minimisation and destruction protocols for sensitive identity items.

The source text sets out duties and prohibitions but does not itself specify penalties, enforcement powers, administrative sanctions or a compliance inspection regime. The instrument prescribes the required conduct and records but contains no express civil or criminal penalties, enforcement agency powers, or infringement notices within the text provided.

What the instrument does indicate about enforcement context

• Cross-reference to other laws. Section 6.4 includes a note referencing Part 5-1A of the Telecommunications (Interception and Access) Act 1979. That note states that under that Act carriage service providers "have an obligation to keep certain information for a specified period of time and to ensure the confidentiality of that information by requiring that the information be encrypted and protected from unauthorised interference or unauthorised access." The inclusion of that note signals that obligations under other Commonwealth statutes may interact with the record-keeping and confidentiality requirements in this instrument (s 6.4 note). However, the instrument does not itself set compliance or enforcement mechanisms under the Telecommunications (Interception and Access) Act.

• Lawful recording exception. Section 6.4(2) allows recording and keeping where that is required or authorised by or under a law. That provision implies providers may be subject to separate legal obligations that require retention or recording beyond what this Determination permits. Any enforcement or penalties tied to those separate laws are not contained in the instrument itself.

Implications from the absence of in-text penalties

• No explicit in-instrument sanctions. Because the provided text contains no express penalties or enforcement mechanisms, any enforcement action for breaches of the obligations in this instrument must logically rely on the broader legal framework or on enforcement mechanisms established elsewhere. The instrument itself does not state what will happen in the event of non-compliance.

• Compliance risk still present. Despite the absence of specified penalties here, the obligations are clear, and failure to comply may trigger enforcement under other statutory regimes or contractual/regulatory consequences, depending on context. The instrument’s references to other Commonwealth laws indicate that compliance does not occur in isolation.

For legal certainty, a practitioner or compliance officer cannot rely on the text provided to identify the sanctioning regime, and should seek the broader instrument or enabling Act, and any relevant legislation that creates enforcement powers or penalties, to determine legal consequences. The provided instrument should be treated as setting operational duties; the enforcement architecture is not included in the text provided.

The instrument explicitly references other Commonwealth legal frameworks and implicitly sits within a broader statutory environment. The text itself contains direct cross-references and notes indicating interactions.

Direct references

• Telecommunications (Interception and Access) Act 1979 (Part 5-1A): The note to s 6.4 states that under Part 5-1A of that Act carriage service providers have obligations to keep certain information for specified periods and to ensure confidentiality of that information, including encryption and protection against unauthorised access or interference. The instrument therefore acknowledges that record-keeping and confidentiality obligations under that Act must be considered when implementing the data-handling rules in s 6.4.

• Commonwealth privacy laws: The note to s 6.4 also states that a carriage service provider’s arrangements for recording and handling personal information must comply with Commonwealth privacy laws where applicable. The instrument therefore expects providers to align their practices with applicable privacy law requirements when handling customer information, even where this Determination sets specific prohibitions on recording and copying.

Interaction features and operational points

• Permitted recording where required by law. Section 6.4(2) provides that the prohibition on recording and keeping government document numbers and category A or B documents does not apply where recording and keeping is "required or authorised by or under a law." That carve-out establishes that statutory obligations in other Acts can override the instrument’s general prohibitions, and requires providers to reconcile conflicting statutory duties by complying with the other law to the extent it requires recording.

• Confidentiality and retention obligations may overlap or conflict. The note regarding Part 5-1A implies carriers have separate obligations to keep certain information and to protect it, potentially creating a layering of retention and protection duties. Providers must map which data must be retained under Part 5-1A and which must be avoided or destroyed under s 6.4, and implement procedures that satisfy both sets of obligations when they both apply.

• Schedule 1 and external standards. Section 4.5 requires that service activators be verified using an "approved method of identity verification specified in column B of Schedule 1." Schedule 1 is outside the provided text. Where Schedule 1 draws on or references other standards, documents or non-statutory guidance, those references will affect compliance. The instrument thus defers to additional material not included here for one of its central verification obligations.

• Interaction with payment systems. Section 6.2 requires providers to keep records linking a carriage service number to a credit or debit card when the purchase was made by card. Practical compliance will involve coordination with payment processors and card acquirers, which are subject to banking, payments and privacy regulation outside this instrument. The instrument does not itself govern payment-system participants but requires record linkage that will involve them.

• Ancillary legal regimes. The instrument’s obligations should be operationalised in the context of other sectors’ rules (for example, anti-money laundering, identity verification standards, or consumer protection laws) even though these are not referenced explicitly in the provided text. The text’s note about Commonwealth privacy law is the explicit pointer to this need to coordinate with other legal regimes.

What is not in the text

• The instrument does not set out comprehensive cross-references to enforcement or penalty provisions in other laws. It does not itself specify how conflicts between its prohibitions and other laws are to be resolved beyond the simple authorisation/requirement exception in s 6.4(2).

• The provided text does not reproduce Schedule 1 or any annexes that may further define approved methods, nor any explanatory memorandum that might explain the drafters’ intentions about interactions.

Practically, providers will need to compare the instrument’s obligations with data-retention and data-protection rules in other statutes and ensure their procedures reconcile any overlapping or conflicting duties. Where other law requires retention of an item this instrument otherwise prohibits, s 6.4(2) permits recording; providers should document the legal basis for such retention and ensure protection measures (for example encryption) are in place to meet the confidentiality expectations noted in s 6.4.

The source text provided does not include an amendment history, commencement notes, repeals, or any indications of prior versions or subsequent changes. The instrument as supplied consists of provisions in s 4.3 (information to be obtained), s 4.4 (verification of identity of purchasers), s 4.5 (verification of identity of service activators), and Part 6 (ss 6.1-6.4 on records). There are references to Schedule 1 and to other statutes, but no schedule content or amendment annotations appear in the text provided.

Implications of the absence of an amendment record in the provided text

• No in-text provenance. Because the provided instrument does not include legislative history, amending instruments, commencement dates or versioning, the reader cannot, from this document alone, tell whether these provisions are the original text, an amendment, or have been amended since initial enactment.

• Need to consult the broader legislative database. Practitioners seeking to understand changes over time, transitional arrangements, or the current force of each provision will need to consult the official legislative database, the enabling Act, the Determination’s preamble and schedule materials, and any amending instruments. The absence of an amendment history here means the instrument alone is insufficient to establish temporal or versional context.

• Schedule 1 omission. The text references Schedule 1 (s 4.5) but does not include it. If Schedule 1 has been amended separately, that would affect the approved method for verifying service activators. Without the schedule, a reader cannot tell whether the approved methods have changed across time.

Recording suggestions where amendment history matters

• When advising operational teams, verify the current consolidated instrument and check for any amending instruments. Because the operational obligations depend on Schedule 1 and on possible amendments to verification standards, practitioners should examine the official consolidated register for the Determination and related materials.

• Document internal compliance versioning. Providers should record which version of the Determination their compliance arrangements implement and build processes to update procedures when amending instruments are promulgated.

In short, the provided text contains no amendment history. Determining whether these provisions have been amended, and tracking Schedule 1 changes, requires consultation of the authoritative legislative repository and ancillary materials.

The provided instrument contains no litigation history, judicial citations, case references, or mention of disputes.

What the absence of litigation history in the text means for practitioners

• No precedent cited. The instrument does not identify any judicial construction or application of these provisions, and no cases are named in the text. Consequently, there is no in-text guidance about how courts or tribunals have interpreted ambiguous terms such as "see" a document, "permitted purpose", or "approved method" in Schedule 1.

• Need to search external sources. Practitioners requiring evidence of how the obligations have been enforced or interpreted by courts must research case law and decisions outside the instrument. The text itself provides no signals about contested issues or settled interpretations.

• Operational uncertainty on interpretive points. Because no litigation history is provided, ambiguities in the text,such as the practical meaning of "see" a document, the standard of satisfaction required in relation to expiry dates, or the scope of "ancillary or incidental" purposes in s 6.4(5)(2),may be open to interpretation until clarified by an authoritative source, whether a regulator’s guidance or judicial decision. Users should document interpretive choices and seek legal advice where necessary.

• Internal record evidence may be decisive. In the absence of litigation precedent, documentation of a provider’s compliance processes and written description of compliance arrangements (s 6.3) will be important evidence if a dispute arises.

Because the instrument contains no litigation history, this section does not summarise cases and instead notes that any litigation landscape must be built from external research, regulator guidance, or subsequent judicial decisions not contained in the provided text.

This instrument contains several operational traps and narrow constraints that providers, compliance officers and advisers should note. These are concrete, source-grounded items that can create practical compliance exposure if overlooked.

1. Different evidence thresholds hinge on an activation count triggered by the new activation. The purchaser-verification regime depends on whether the activation "will result in the purchaser having 5 or more activated prepaid mobile carriage services" (Table 3). Providers must determine the purchaser’s current activated count and whether the new activation crosses the 5-service trigger before selecting the verification pathway. Failing to compute this correctly could lead to applying the lower evidentiary standard when the higher standard was required (Table 3, items 1-2).

2. Payment by credit or debit card can materially reduce documentary requirements for purchasers. Where activation will not result in five or more services and the purchaser offers to pay by credit or debit card, the provider is, in certain circumstances, not required to take any further verification steps (Table 3, item 1, note). That exception only applies in the limited factual matrix specified; providers must ensure the payment method is recorded and link the card to the service number where verification occurred under s 4.4 and payment was by card (s 6.2).

3. Obligation to link card-paid purchases to the service number. Section 6.2 requires a record that links the carriage service number to the credit or debit card used when s 4.4 was complied with and payment was by card. The instrument suggests using a transaction code as the linking mechanism rather than storing the actual card number (s 6.2 note); storing full card details may breach other laws and the instrument’s spirit, and may contravene s 6.4(1) where it concerns prohibited recordings.

4. Strict limits on recording government document numbers and documents. Section 6.4(1) broadly prohibits recording and keeping the identifying number of a government document and category A or B documents. Providers must carefully design systems to avoid storing these items except where s 6.4(2) or s 6.4(3) allow it. Copying or reproducing documents containing prohibited information is also forbidden (s 6.4(4)). Providers that have historically taken copies of identity documents at point of sale must revise procedures.

5. Narrow permitted-purpose exception requires immediate destruction. If a government document number is recorded for a permitted purpose (s 6.4(3)), the provider must destroy the number immediately after verifying the service activator’s identity (s 6.4(3)(3)). "Immediately" will be an operational constraint and should be reflected in systems that allow transient temporary tokens without persistent storage.

6. The "permitted purpose" definition is narrow. Section 6.4(5) defines permitted purpose to include verifying the identity of a service activator under s 4.5 and ancillary or incidental matters. It does not, on its face, extend permitted-purpose recording to purchasers under s 4.4. Consequently, temporary recording exceptions are framed around s 4.5 verification processes for service activators.

7. Foreign military ID card handling requirement. If a category A document is a foreign military ID card, the document must be shown at an access-controlled defence site (s 4.4(3)(b)). Providers must plan for this location constraint and avoid accepting such documents in regular retail locations.

8. The approved method for service activators is external. Section 4.5 requires use of an approved method specified in Schedule 1, column B. The provided text does not include Schedule 1. Absent that schedule, providers cannot fully implement the service activator verification path or know whether the approved method is an in-person check, online verification, or a set of documents.

9. Retention period tied to service activation. Records must be kept "for as long as the service is activated" (s 6.1(2)). Providers must manage lifecycle processes that delete or archive records promptly when the service is deactivated, subject to any other statutory retention requirements that may require different retention periods under other law (s 6.4(2) note).

10. Lack of specified sanctions in the instrument. The instrument does not set out penalties or an enforcement regime. That absence does not negate the operational imperative to comply, but it complicates compliance-risk modelling because the text does not specify regulatory responses to breaches.

11. Copy prohibition may hinder usual compliance practices. Many providers and resellers routinely copy identity documents to support disputes or fraud investigations. Section 6.4(4) prohibits copying or reproducing documents containing prohibited information, requiring procedural change and alternative evidence chains for later dispute handling.

12. Written description must be kept. Section 6.3 requires a written description of compliance arrangements. This is a discrete, auditable item that should be version-controlled and readily producible.

13. Interaction with legal retention obligations. Section 6.4(2) allows recording where required or authorised by law. Providers must be prepared to justify any deviation from the general prohibition by documenting the legal basis for retention under other statutes.

Careful policy design, robust system architecture for ephemeral tokens, and documented legal rationales are necessary to avoid these operational gotchas.

Below are concrete, source-grounded steps and operational controls that a carriage service provider should implement to meet the instrument’s obligations. Each step references the relevant provision in the source text.

1. Map customer role flows and determine applicable requirements (Table 2; s 4.4; s 4.5)

   • Categorise each customer interaction at intake as either a purchaser or a service activator. Use the items in Table 2 to collect the required basic information immediately: purchaser’s name, residential address if not acting for an entity, the number of other activated prepaid services supplied to that purchaser, and entity name/business address where applicable; for a service activator collect name, date of birth, residential address if not acting for an entity, and entity name/business address where applicable (Table 2).
   • Implement a decision-tree that tests whether the new activation will result in the purchaser having five or more activated prepaid services. This trigger determines which verification pathway in Table 3 applies.

2. Implement purchaser verification procedures in accordance with Table 3 (s 4.4)

   • If the new activation will not result in five or more activated services and payment is by credit or debit card, document the payment method and note that no further verification steps are required (Table 3, item 1, note).
   • If the activation would not result in five or more services and payment is not by card, adopt a process to visually "see" either one category A document or two category B documents of differing kinds and to record completion of the verification check (Table 3, item 1).
   • If the activation will result in five or more active services, implement procedures for seeing two category A documents of different kinds, or one category A and two category B documents of different kinds; ensure staff can recognise and record which documents were seen (Table 3, item 2).
   • Ensure staff check expiry dates and refuse expired documents (s 4.4(3)(a)). Create a checklist that staff sign when they "see" documents, including the document type and unique identifiers if permitted by law to record them.

3. Implement service activator verification using approved methods (s 4.5)

   • Obtain Schedule 1 (column B) and document the approved methods. Adopt and operationalise the approved method(s) for verifying service activators, whether those are online identity-verification APIs, in-person checks, or other methods. If Schedule 1 is not yet obtained, treat s 4.5 as incomplete and seek authoritative Schedule 1 for operationalisation (s 4.5).
   • Treat the service activator permitted-purpose recording pathway in s 6.4(3) as available only within the specific permitted-purpose limits; do not use that pathway for purchasers unless another law authorises it.

4. Data-handling and record-keeping: implement retention and minimisation rules (ss 6.1-6.4)

   • Keep compliance records for each prepaid mobile carriage service sufficient to enable compliance to be readily ascertained (s 6.1(1)). These records should document which verification pathway was used, which documents were seen, and timestamps for verification actions.
   • Retain those records only for as long as the service is activated, and implement automated processes to flag deactivation and remove or archive records accordingly (s 6.1(2)).
   • For purchases made with a credit or debit card where s 4.4 applied, keep a linking record between the carriage service number and the card used (s 6.2(2)). Use a transaction code or tokenised reference rather than storing card numbers where possible, consistent with the instrument’s own example (s 6.2 note).
   • Maintain a written, version-controlled description of the arrangements the provider has in place to comply with the Determination, and store it where it can be produced for audit or inspection (s 6.3).

5. Implement strict prohibitions, exceptions and destruction procedures (s 6.4)

   • Do not record or keep the identifying number of government documents or category A or B documents except where authorised by law or where the narrow s 6.4(3) permitted-purpose exception applies (s 6.4(1)-(3)).
   • Do not copy or reproduce documents that contain information that must not be recorded and kept (s 6.4(4)). Remove or rework existing practices that retain scanned copies of identity documents containing prohibited items.
   • Where a permitted-purpose temporary recording is used (for example, to assist a customer after failed online verification), implement a secure ephemeral store with automatic destruction immediately after verification, and retain logs showing destruction timestamps and the legal ground for the temporary recording (s 6.4(3)).
   • Where recording is required or authorised under another law, document the legal authority (s 6.4(2)) and ensure that recordings are protected in accordance with any other statute referenced, such as encryption and access controls (s 6.4 note referencing Part 5-1A of the Telecommunications (Interception and Access) Act).

6. Special-case controls

   • Do not accept foreign military ID cards at common retail points. If a foreign military ID card is presented as category A identification, ensure the process routes the presentation to an access-controlled defence site as required by s 4.4(3)(b).
   • For card payments where the purchaser benefits from the reduced verification pathway, ensure the payment instrument is validated and recorded at the point of sale to establish entitlement to the reduced verification burden (Table 3, item 1, note).

7. Training, audit and documentation

   • Train staff on the difference between purchasers and service activators, the triggers that increase verification thresholds (five activated services), the document combinations required, and the strict non-recording and copying rules in s 6.4.
   • Maintain an audit trail that demonstrates compliance: which documents were seen (record the type but not prohibited numbers), which verification method was used, the link token for card-paid sales where relevant, and the location/time of verification.
   • Ensure the written description of compliance arrangements (s 6.3) is kept current and includes the decision logic used in the intake questionnaire that determines which verification path applies.

8. Systems and third-party interactions

   • Where verification uses third-party services (for example, identity verification APIs or payment processors), ensure contractual terms permit the required data flows without contravening s 6.4, and that third parties will delete or not retain prohibited data where the Determination forbids it.
   • Use tokenisation for card-linking records to meet s 6.2 without storing card PANs. Document the token mapping logic and retention schedule consistent with s 6.2 and the temporary retention rules in s 6.4(3) where applicable.

9. Legal monitoring and update process

   • Because Schedule 1 and any external laws affect compliance, institute a process for monitoring legislative updates and amending instruments that could change the approved methods or the interaction with other statutory retention obligations (s 4.5; s 6.4(2) note).

10. Produce demonstrable evidence

• Retain documentary evidence that the provider complied with the required verification step for each activation, including the trigger analysis for the five-service threshold, payment method evidence for card payments, written compliance-arrangement description (s 6.3), and the card-to-service link where applicable (s 6.2).

These steps operationalise the source provisions and create a defensible, auditable compliance posture. Where the instrument’s text defers to other material (for example, Schedule 1), obtain and follow those materials before finalising procedures.