Network Tokenization API
Copy page
Copy page as Markdown for LLMs
Open in ChatGPT
Ask questions about this page
Open in Claude
Ask questions about this page
Network Tokenization provides enhanced security and improved authorization rates by replacing sensitive card data with network-issued tokens. These tokens are uniquely tied to specific merchants and include dynamic cryptograms for each transaction, offering superior protection against fraud while maintaining seamless payment experiences.
Network Tokenization is only available for PCI-certified merchants implementing PCI-certified custom integration.
Prerequisites
Before implementing external network tokenization with Amazon Payment Services, merchants must complete the following prerequisites:
Account Setup Requirements
-
Service Activation: Ensure that external network tokenization is activated on your merchant account.
-
Token Authority Integration: Complete integration with the external token authority service provided by the card scheme (Visa, Mastercard, etc.).
-
PAN Provisioning: Provision the Primary Account Numbers (PANs) to obtain the corresponding network tokens from the card schemes.
-
Cryptogram Generation: Implement capability to generate cryptograms for the network tokens prior to sending them to Amazon Payment Services.
-
Webhook Configuration: Set up a notification webhook to receive updates from the schemes regarding any changes to card or token statuses.
Network tokenization requires additional integration with card scheme token authorities. Contact your Amazon Payment Services integration team for setup assistance.
API Endpoints
https://sbpaymentservices.payfort.com/FortAPI/paymentApi
Request Format
- Method:
POST
- Content-Type:
application/json
- Submission: Server-to-server HTTPS POST
Request Parameters
Use the same parameters as PCI-certified custom integration with the addition of the network_token
object:
Network Token Object
Parameter |
---|
token String Max: 19 Required Network token issued by the card scheme authority. Example. 4000000000001234 |
token_expiry_date String Max: 4 Required Network token expiry date in YYMM format. Example. 2512 |
token_cryptogram String Max: 40 Required Base64-encoded cryptogram generated by the card network for this specific transaction. Must be unique for each transaction. Example. AgAAAAAAAIR8CQrXcIhbQAAAAAA= |
The token_cryptogram is a one-time-use security code generated by the card network (Visa, Mastercard) when using a network token for a transaction. It must be unique for each transaction even with the same network token. Maximum length is approximately 28-40 characters when base64-encoded.
{
"command": "PURCHASE",
"access_code": "zx0IPmPy5jp1vAz8Kpg7",
"merchant_identifier": "CycHZxVj",
"merchant_reference": "ORD-2024-001",
"amount": "25000",
"currency": "AED",
"language": "en",
"customer_email": "customer@example.com",
"recurring_mode": "UNSCHEDULED",
"agreement_id": "AGR123",
"card_number": "4005550000000001",
"expiry_date": "2512",
"card_security_code": "123",
"network_token": {
"token": "4000000000001234",
"token_expiry_date": "2512",
"token_cryptogram": "AgAAAAAAAIR8CQrXcIhbQAAAAAA="
},
"signature": "7cad05f0212ed933c9a5d5dffa31661acf2c827a"
}
{
"command": "PURCHASE",
"access_code": "zx0IPmPy5jp1vAz8Kpg7",
"merchant_identifier": "CycHZxVj",
"merchant_reference": "ORD-2024-001",
"amount": "25000",
"currency": "AED",
"language": "en",
"customer_email": "customer@example.com",
"fort_id": "149295435400084008",
"payment_option": "VISA",
"response_message": "Success",
"response_code": "14000",
"status": "14",
"network_token": {
"token": "4000000000001234",
"token_expiry_date": "2512",
"token_cryptogram": "AgAAAAAAAIR8CQrXcIhbQAAAAAA="
},
"signature": "7cad05f0212ed933c9a5d5dffa31661acf2c827a"
}
Response Parameters
Network tokenization returns the same response parameters as PCI-certified custom integration with the additional network_token
parameter object containing the tokenization details used in the transaction.
Additional Response Parameters
Parameter |
---|
network_token Object Network token object containing the tokenization details used in the transaction. Example. See network_token object below |
token String Max: 19 Network token that was used in the transaction. Example. 4000000000001234 |
token_expiry_date String Max: 4 Network token expiry date in YYMM format. Example. 2512 |
token_cryptogram String Max: 40 Base64-encoded cryptogram that was used for this transaction. Example. AgAAAAAAAIR8CQrXcIhbQAAAAAA= |
Testing The Integration
Use the sandbox environment for development and testing:
- Payment API URL:
https://sbpaymentservices.payfort.com/FortAPI/paymentApi
- Test Cards: Use our comprehensive Testing Cards
Go-Live Process
When ready to move to production, follow our Go-Live checklist for complete production readiness guidelines.
Response Codes
For a complete list of response codes and their descriptions, please refer to our Error Codes Documentation.