TPPP Geolocation Data Enhancement (PayFac Compliance)

This data identifies the physical location associated with the transaction and the entities involved in processing the payment.

Merchants operating as payment facilitators (PayFacs) or aggregators must supply this information when submitting transactions on behalf of sub-merchants.

Implementation Summary

You must update your PayHost integration to include the following additional request elements:

Acceptor Geolocation
Service Geolocation
Facilitator Information

No changes are required to response handling.

Geolocation Types

Two types of location data are required.

Acceptor Geolocation

Represents the primary headquarters or main office of the merchant or payment facilitator.

Service Geolocation

Represents the physical location where the transaction originates (for example, a store branch, terminal location, or service point).

A merchant may operate multiple terminals under a single Merchant ID (MID).
Compliance is achieved as long as the service location data is provided for each transaction.

Geolocation Data Structure

The Acceptor and Service geolocation elements use the same schema.

WSDL Type: `GeolocationType`

<Geolocation>
  <Address>240 Main Road Rondebosch</Address>
  <City>Durban</City>
  <State>KZN</State>
  <Country>ZA</Country>
  <Zip>6005</Zip>
  <MSISDN>27871501001</MSISDN>
  <CustomerServiceMSISDN>27871501001</CustomerServiceMSISDN>
  <AdditionalContactInformation>Operational Hours: 08:00 - 17:00</AdditionalContactInformation>
  <URL>www.example.co.za</URL>
</Geolocation>

Geolocation Fields

Field	Description	Required	Type
Address	Full physical address	Yes	String
City	City name	Yes	String
State	Province or region code	Yes	String (Alpha-3)
Country	ISO Alpha-2 country code	Yes	String
Zip	Postal code	Yes	Numeric string
MSISDN	Contact phone number	Yes	Numeric string
CustomerServiceMSISDN	Customer service phone number	Acceptor only	Numeric string
AdditionalContactInformation	Additional contact details or operating hours	Optional	String
URL	Website address	Yes	String

Facilitator Information

Payment facilitators must provide information about the entity processing payments on behalf of sub-merchants.

WSDL Type: `FacilitatorType`

<Facilitator>
  <PaymentFacilitatorId>261517</PaymentFacilitatorId>
  <AcceptorTaxId>1234567890</AcceptorTaxId>
  <SubMerchantId>2245</SubMerchantId>
  <SubMerchantName>Steers The Pavilion Lane 1</SubMerchantName>
  <SubMerchantTaxId>1234567890</SubMerchantTaxId>
  <IndependentSaleOrg>Hourglass</IndependentSaleOrg>
  <FacilitatorName>Hourglass</FacilitatorName>
</Facilitator>

Facilitator Fields

Field	Description	Required	Type
PaymentFacilitatorId	Identifier of the payment facilitator	Yes	Numeric string
AcceptorTaxId	Tax ID of the facilitating merchant	Yes	Numeric string
SubMerchantId	Identifier of the sub-merchant	Yes	Numeric string
SubMerchantName	Name of the sub-merchant	Yes	String
SubMerchantTaxId	Tax ID of the sub-merchant	Yes	Numeric string
IndependentSaleOrg	Name of the ISO (if applicable)	Yes	String
FacilitatorName	Name of the third-party facilitator	Yes	String

When This Is Required

Geolocation and facilitator data must be included when:

Processing payments on behalf of sub-merchants
Operating as a payment facilitator or aggregator
Required for scheme or regulatory compliance
Requested by PayGate or the acquiring bank

Example Use Case

A payment platform processes transactions for multiple retail stores using a single merchant account. Each store location must provide its own service geolocation data, while the facilitator provides its organisational details.

WSDL Reference

For full schema definitions, refer to the PayHost WSDL:

https://secure.paygate.co.za/payhost/process.trans?wsdl