Skip to content
My Docs

Request Configuration For FAC

PowerTrans API Integration Documentation

Overview

These functions are essential for interacting with the First Atlantic Commerce (FAC) PowerTrans API. They handle the creation of request bodies and headers for various types of transactions.

Functions:

  1. firstSaleRequestBody:

    • Purpose: Generates a request body for the first sale transaction.
    • Parameters:
      • panToken: Token representing the fac pan token from the tokenization request.
      • billingDetails: Billing information.
      • totalAmount: Transaction amount.
    • Returns: An object formatted as per the FAC API requirements.

  2. tokenizationBody:

    • Purpose: Creates a request body for card tokenization.
    • Parameters:
      • cardData: Card information (number, cvv, expiry date).
      • currencyCode: Currency code for the transaction.
    • Returns: An object for tokenization request.

  3. recurringPaymentBody:

    • Purpose: Prepares a request body for recurring payments.
    • Parameters: Similar to firstSaleRequestBody.
    • Returns: An object tailored for recurring payment requests.

  4. getHeaders:

    • Purpose: Configures the request headers for general API calls.
    • Returns: An object containing headers, including authentication credentials.

  5. getTokenHeaders:

    • Purpose: Sets up headers specifically for tokenization requests.
    • Returns: An object with headers configured for tokenization.

Important Notes:

  • These functions utilize environment variables for authentication, ensuring credentials are not hard-coded.
  • The TransactionIdentifier and OrderIdentifier are uniquely generated for each request.
  • The firstSaleRequestBody includes 3D Secure parameters, critical for enhanced security in transactions.
  • The recurringPaymentBody sets ThreeDSecure to false, as per recurring payment requirements.

Usage:

These functions are crucial in the backend for making secure, compliant requests to FAC’s PowerTrans API for various payment-related operations, including tokenization, first-time sales, and recurring payments. Ensure to keep the environment variables updated and secure.