Skip to main content

Overview

Payment methods in Gu1 are represented as entities of type payment_method. This allows you to track credit cards, bank accounts, wallets, and other payment instruments associated with persons or companies.
Payment methods are created using the universal /entities endpoint with entityType: "payment_method".

What is a Payment Method Entity?

A payment method entity represents any financial instrument used for transactions:
  • Credit Cards - Visa, Mastercard, Amex, etc.
  • Debit Cards - Bank-issued debit cards
  • Bank Accounts - Checking, savings accounts
  • Digital Wallets - PayPal, Apple Pay, Google Pay, etc.
  • Cryptocurrency Wallets - Bitcoin, Ethereum addresses

Key Features

Entity Relationships

Payment methods can be linked to other entities:
  • Owned by - Link to the person or company owner
  • Used in - Link to transactions where this payment method was used
  • Associated with - Link to devices used for transactions

Risk Analysis

Payment methods can be analyzed for fraud detection:
  • Transaction velocity monitoring
  • Geographic anomaly detection
  • Device fingerprinting correlation
  • Historical usage patterns

Use Cases

  1. Fraud Detection - Detect suspicious payment method usage patterns
  2. Card Verification - Validate card details and ownership
  3. Account Monitoring - Track unusual account activity
  4. Transaction Tracking - Link transactions to payment sources
  5. Multi-account Detection - Identify shared payment methods across users

Data Structure

Payment method entities contain:

Payment Method Types

Credit Card

Bank Account

Digital Wallet

Cryptocurrency Wallet

API Endpoints

Payment method entities use the standard entity endpoints:

Common Patterns

Creating a Payment Method for a Person

Checking Payment Method Usage

Find all transactions using a specific payment method:

See Also