Appearance
Prerequisite Information
This part of the Payment Specification documentation outlines the process for implementing a client. A client is defined as any tool that is capable of performing interactions with a Payment Gateway.
TIP
Keep the following in mind:
- Clients should refuse to interact with Gateways that do not use HTTPS and at least TLS 1.2.
- Clients must store secret keys and authorization tokens in encrypted storage (ie. Keychain).
Getting Started
Clients should first attempt to authenticate a user to access other information and facilitate purchases on device. The Authentication section outlines the process for authenticating a user.
When making requests to a gateway, there is an exhaustive list of headers that must be passed. These help the Gateway to identify the client and accordingly execute domain specific logic.
yaml
X-Repository-URI: https://apt.tale.me
Sec-CH-UA-Arch: iphoneos-arm64
Sec-CH-UA-Bitness: 64
Sec-CH-UA-Model: iPhone11,9
Sec-CH-UA-Mobile: ?1 # 0 = false, 1 = true
Sec-CH-DPR: 3 # Screen scale
Sec-CH-UA-Platform: iphoneos
Sec-CH-UA-Platform-Version: 15.4.1
Sec-CH-UA: Sileo;v=2.4.4;t=client,dopamine;v=1.0.1;t=jailbreak,procursus;t=distribution