Pelecard Gateway Integration for Make.com

This guide explains how to use the Pelecard Gateway custom app for Make.com (formerly Integromat). With this integration, you can automate payment processes, manage transactions, and receive real-time notifications about payment events.

Getting Started

Before you begin, make sure you have:

• An active Pelecard merchant account
• API credentials (Terminal number, Username, and Password)
• A Make.com account (paid plan required — custom apps are not available on free plans)

Installing the Pelecard Gateway App

The Pelecard Gateway is a custom app that needs to be added to your Make.com organization. Click the link below to install it:

Install Pelecard Gateway App

After clicking the link:

1. Log in to your Make.com account (if not already logged in)
2. Accept the app invitation
3. The Pelecard Gateway app will be added to your organization
4. You can now use it in any scenario by searching for “Pelecard Gateway”

Setting Up Connection

When you add any Pelecard module to your scenario for the first time, you’ll need to create a connection. This connection securely stores your API credentials and will be reused across all Pelecard modules.

Connection Parameters

Note: If you’re using a test environment, change the Base URL to your sandbox endpoint.

Available Modules

Create a Payment Process

Action

Generates a payment URL for a customer to complete payment with card details. Use this module to create hosted payment pages for your customers.

Input Parameters

Output

Returns a JSON response containing:

• URL — Payment page URL to send to your customer
• ConfirmationKey — Unique transaction identifier
• Error — Error details if the request failed

Example: Creating a Payment Link

To create a ₪150 payment with token generation:

• Amount: 150
• Currency: ILS
• Create Token: Yes
• ParamX: ORDER-12345
• Webhook URL: [Your Watch Transactions webhook URL]

Debit by Token

Action

Charges a customer using a previously saved Pelecard token. Supports three payment modes: Regular (single payment), Installments, and Credit.

Input Parameters

3D Secure Parameters (advanced):

• ECI — Electronic Commerce Indicator
• XID — Transaction identifier
• CAVV — Cardholder Authentication Verification Value

Output

Example: Charging a Subscription

To charge ₪99 monthly subscription:

• Token: [Token from previous payment]
• Amount: 99
• Mode: Regular
• Param X: SUB-2024-001

Get Transaction Details

Action

Retrieves complete information about a specific transaction using its unique identifier.

Input Parameters

Output

Returns complete transaction data including:

• StatusCode — Response status
• ResultData — Transaction details:
  • ConfirmationKey
  • Token (masked)
  • CreditCardNumber (masked)
  • Amount, Currency
  • Transaction date and time
  • Approval number
  • ParamX (your custom data)
• ErrorMessage — Error description if failed

Cancel Transaction

Action

Cancels (voids) an existing transaction. Can only be used for transactions that haven’t been settled yet.

Input Parameters

* At least one identifier is required — either Transaction UID or Debit Transaction ID.

Output

• StatusCode — Response code (000 = success)
• ErrorMessage — Error description if cancellation failed

Important Notes

• Transactions can only be cancelled before settlement (typically same business day)
• After settlement, use a refund process instead

Search Transactions

Search

Search and retrieve multiple transactions within a date range. Returns an array of transactions that can be processed individually in your scenario.

Input Parameters

Output (per transaction)

Returns an array of transactions. Each transaction contains:

Example: Daily Transaction Report

Create a scenario that runs daily and exports all transactions to Google Sheets:

1. Trigger: Schedule (daily at 9:00 AM)
2. Pelecard: Search Transactions (yesterday’s date)
3. Google Sheets: Add rows with transaction data

Make an API Call

Action

Make a custom API call to any Pelecard endpoint. Use this module for advanced operations not covered by other modules, or when you need direct access to Pelecard’s API.

Input Parameters

How It Works

The module automatically:

• Prepends the Base URL from your connection (e.g., https://gateway21.pelecard.biz/)
• Adds authentication credentials (terminal, user, password) to the request body
• Merges your custom JSON body with the credentials

Output

Example: Custom API Request

To call GetTransaction endpoint directly:

• Endpoint URL: PaymentGW/GetTransaction
• Method: POST
• Body: {"TransactionId": "12345678"}

The final request will include your credentials automatically:

{
  "terminal": "your-terminal",
  "user": "your-username", 
  "password": "your-password",
  "TransactionId": "12345678"
}

Common Endpoints

Watch Transactions

Instant Trigger

Receives real-time notifications from Pelecard when payment events occur. This webhook-based trigger starts your scenario immediately when a customer completes (or fails) a payment.

Setup Instructions

1. Add the “Watch Transactions” module as the first module in your scenario
2. Create or select your Pelecard connection
3. Click “Save” — Make.com will generate a unique webhook URL
4. Copy the webhook URL
5. Use this URL in the “Create a Payment Process” module as the Webhook URL parameter
6. Activate your scenario

How It Works

When you create a payment using “Create a Payment Process” with the webhook URL:

1. Customer receives the payment link
2. Customer completes (or cancels) the payment
3. Pelecard sends transaction data to the webhook URL
4. Your Make.com scenario triggers instantly with all transaction details

Output Data

When triggered, this module outputs the following fields:

Checking Payment Success

Use the isSuccess field or check if statusCode equals “000” to determine if the payment was successful:

• statusCode = "000" → Payment successful
• statusCode ≠ "000" → Payment failed (check statusDescription for details)

Example: Saving Token for Future Payments

If you enabled “Create Token” in the payment process, the webhook will return the token. Save it to charge the customer later:

1. Trigger: Watch Transactions
2. Filter: Only continue if isSuccess = true AND token is not empty
3. Database/CRM: Save the token with customer record

Common Use Cases

1. Send Payment Link via Email

Create a scenario that generates a payment link and automatically sends it to your customer:

1. Trigger: New row in Google Sheets / New order in your system
2. Pelecard: Create a Payment Process
3. Email: Send the payment URL to customer

2. Automatic Subscription Billing

Charge customers automatically on a schedule:

1. Trigger: Schedule (monthly)
2. Database: Get customers with active subscriptions
3. Pelecard: Debit by Token
4. Action: Update subscription status / Send receipt

3. Real-time Payment Notifications

Get notified instantly when payments are completed:

1. Trigger: Watch Transactions (Pelecard webhook)
2. Action: Send Slack notification / Update CRM / Create invoice

4. Complete Payment Flow with Token Storage

Full flow: create payment → receive webhook → save token for future charges:

1. Scenario A (Payment Creation):
   • Trigger: New order from your system
   • Pelecard: Create a Payment Process (with Create Token = Yes)
   • Action: Send payment link to customer
2. Scenario B (Webhook Handler):
   • Trigger: Watch Transactions
   • Filter: isSuccess = true
   • Action: Save token to database with customer ID (using ParamX)

Troubleshooting

Connection Failed

• Verify your Terminal number, Username, and Password are correct
• Check that your IP address is whitelisted in Pelecard settings
• Ensure the Base URL matches your environment (production vs. sandbox)

Transaction Declined

• Check the error code returned in the response
• Verify the amount format (should be in agorot, not shekels)
• Ensure the token is valid and not expired

Webhook Not Triggering

• Verify the webhook URL is correctly configured in Pelecard
• Check that your Make.com scenario is active (not paused)
• Review the webhook logs in Make.com for any errors