Pagar.me Payment icon

Pagar.me Payment

Interact with Pagar.me API for payments
Join our community

Actions6

Overview

This node interacts with the Pagar.me API to tokenize credit card information securely. It converts sensitive card details into a token that can be used for subsequent payment transactions without exposing the actual card data. This is useful for scenarios where you want to securely store or reuse card information for payments, such as in e-commerce platforms or subscription services.

Use Case Examples

  1. Tokenizing a customer's credit card details to store a token for future payments.
  2. Converting card data into a token to comply with PCI DSS requirements by avoiding direct handling of card information.

Properties

Name Meaning
Card Number Card primary account number (PAN) without spaces.
Holder Name Full name of the card holder.
Holder Document Document number (CPF/CNPJ) of the card holder.
Expiration Month Two-digit expiration month (MM) of the card.
Expiration Year Two-digit expiration year (YY) of the card.
CVV Card security code.
Brand Card brand, e.g., Visa, MasterCard.

Output

JSON

  • card
    • id - The unique identifier of the tokenized card returned by the Pagar.me API.
    • brand - The brand of the card (e.g., Visa, MasterCard).
    • last_digits - The last digits of the card number for reference.
    • holder_name - The name of the card holder as provided.
    • exp_month - Expiration month of the card.
    • exp_year - Expiration year of the card.

Dependencies

  • Pagar.me API

Troubleshooting

  • Ensure the Public Key (pk_...) is configured in the credentials; it is required for tokenization and missing it will cause an error.
  • Verify that all required card details are provided and correctly formatted, especially the card number, expiration date, and CVV.
  • Check for network connectivity issues or API rate limits that might cause request failures.
  • Error messages from the Pagar.me API will include HTTP status codes and details; review these to identify issues such as invalid credentials, malformed requests, or unsupported card brands.

Links

Discussion