Skip to main content
Powertranz is a payment gateway that provides payment processing solutions for merchants in the Caribbean and Latin America. The platform supports card payments with features like delayed capture, partial refunds, 3-D Secure authentication, and payment method tokenization across multiple currencies and countries.

​
Setup

Speak to your Powertranz account manager to obtain your credentials. See the Powertranz documentation for more information.

​
Credentials

When setting up Powertranz in the dashboard, configure the following credentials:
  • Powertranz ID - Your merchant account identifier, for example 99901066.
  • Powertranz Password - Your merchant account’s unique password.
  • Powertranz Gateway Key (optional) - An additional token provided by Powertranz. Only set this if provided by Powertranz.

​
Connector configuration

After setting up your Powertranz connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure Powertranz as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the Powertranz connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Capabilities

​
Supported countries

​
Supported currencies

​
Limitations

This is a closed-loop connector. Some failover scenarios are limited. For details, see Open-loop versus closed-loop.

​
Integration

To accept card payments with Powertranz, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
Powertranz also supports a server-side card integration for PCI Level 1 compliant merchants.

​
3-D Secure

By default, the Powertranz connector attempts 3DS authentication for every card transaction. To skip 3DS for a specific transaction, pass the skipThreeDSecure connection option. 
var transaction = await client.Transactions.CreateAsync(
  transactionCreate: new TransactionCreate()
  {
    Amount = 1299,
    Currency = "TTD",
    ConnectionOptions = new TransactionCreateConnectionOptions()
    {
      PowertranzCard = new ConnectionOptionsPowertranzCard()
      {
        SkipThreeDSecure = "true",
      },
    },
    Country = "TT",
    PaymentMethod =
      TransactionCreatePaymentMethod.CreateCheckoutSessionWithUrlPaymentMethodCreate(
        new CardPaymentMethodCreate()
        {
          Method = "card",
          Number = "4111111111111111",
          ExpirationDate = "12/30",
          SecurityCode = "123",
        }
      ),
  }
);

connectionOptions := components.TransactionCreateConnectionOptions{
  PowertranzCard: &components.ConnectionOptionsPowertranzCard{
    SkipThreeDSecure: gr4vy.String("true"),
  },
}

transactionCreate := components.TransactionCreate{
  Amount:            amount,
  Currency:          currency,
  Country:           &country,
  ConnectionOptions: &connectionOptions,
  PaymentMethod:     &paymentMethod,
}

transaction, err := client.Transactions.Create(ctx, transactionCreate, nil, nil, nil)

CreateTransactionResponse transactionResponse = gr4vyClient.transactions().create()
  .transactionCreate(TransactionCreate.builder()
    .amount(1299L)
    .currency("TTD")
    .connectionOptions(TransactionCreateConnectionOptions.builder()
      .powertranzCard(ConnectionOptionsPowertranzCard.builder()
        .skipThreeDSecure("true")
        .build())
      .build())
    .country("TT")
    .paymentMethod(TransactionCreatePaymentMethod.of(CardPaymentMethodCreate.builder()
      .method("card")
      .number("4111111111111111")
      .expirationDate("12/30")
      .securityCode("123")
      .build()))
    .build())
  .call();

$transactionCreate = new TransactionCreate(
  amount: 1299,
  currency: 'TTD',
  country: 'TT',
  connectionOptions: new TransactionCreateConnectionOptions(
    powertranzCard: new ConnectionOptionsPowertranzCard(
      skipThreeDSecure: 'true'
    )
  ),
  paymentMethod: new CardPaymentMethodCreate(
    method: 'card',
    number: '4111111111111111',
    expirationDate: '12/30',
    securityCode: '123'
  )
);
$response = $client->transactions->create($transactionCreate);

transaction: models.Transaction = client.transactions.create(
  amount=1299,
  currency="TTD",
  country="TT",
  connection_options={
    "powertranz-card": {
      "skip_three_d_secure": "true",
    },
  },
  payment_method={
    "method": "card",
    "number": "4111111111111111",
    "expiration_date": "12/30",
    "security_code": "123",
  }
)

const transaction = await client.transactions.create({
  amount: 1299,
  currency: "TTD",
  country: "TT",
  connectionOptions: {
    "powertranz-card": {
      skipThreeDSecure: "true",
    },
  },
  paymentMethod: {
    method: "card",
    number: "4111111111111111",
    expirationDate: "12/30",
    securityCode: "123"
  }
})
To test Powertranz 3DS, refer to their documentation which lists various test cards.
When 3DS is enabled, Powertranz may perform a redirect to authenticate the card, even when the card is not enrolled in 3DS. This redirect completes frictionless without the buyer’s explicit approval.

​
Recurring payments

Powertranz does not support open loop payments. It does support recurring payments with the payment_source set to either card_on_file or recurring. For customer-initiated (CIT) payments, no additional data is required. For merchant-initiated (MIT) payments with either card_on_file or recurring, pass the scheme_transaction_id from the previous transaction as the previous_scheme_transaction_id on the new transaction.
The previous_scheme_transaction_id only needs to be sent if merchant_initiated is set to true. Always send the scheme_transaction_id returned in the response for the previous transaction in the series.