> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get payment

> > 🚧 Beta
> This is a Beta endpoint. Feedback from the community is welcome. We may make breaking changes to this endpoint.

Get a payment by ID.




## OpenAPI

````yaml openapi-v2.json get /payments/{payment_id}
openapi: 3.0.3
info:
  description: >
    <h2>Let's build something great.</h2><p>Welcome to the official reference
    documentation for Synctera APIs. Our APIs are the best way to automate your
    company's banking needs and are designed to be easy to understand and
    implement.</p><p>We're continuously growing this library and what you see
    here is just the start, but if you need something specific or have a
    question, <a class='text-blue-600' href='https://synctera.com/contact'
    target='_blank' rel='noreferrer'>contact us</a>.</p>
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0.html
  title: Synctera API
  version: v2
servers:
  - description: Production
    url: https://api.synctera.com/v2
  - description: Sandbox (no real world financial impact)
    url: https://api-sandbox.synctera.com/v2
security:
  - bearerAuth: []
tags:
  - description: Request to create and manage edd
    name: Trust
  - description: Requests to calculate and manage CRR
    name: CRR
  - description: Requests to issue and manage cards
    name: Cards
  - description: Push and pull from cards
    name: External Cards
  - description: Bulk card issuance
    name: Bulk Issuance
  - description: Requests to generate simulated transactions
    name: Card Transaction Simulations
  - description: Requests to generate simulated webhooks
    name: Card Webhook Simulations
  - description: Requests to create and manage card disputes
    name: Card Disputes
  - description: Requests to simulate card payments
    name: Card Simulations
  - description: Create and manage documents.
    name: Documents
  - description: Request to create and manage payment_schedules
    name: Cronut
  - description: Apple Pay APIs
    name: Apple Pay
  - description: Request to create and manage accounts
    name: Accounts
  - description: Account Template
    name: Account Templates
  - description: >-
      Account programs define configurations for payment rails and transaction
      capabilities across different account types.
    name: Account Programs
  - description: Requests to create and manage account products, including fees, interest.
    name: Account Products
  - description: |
      The internal account resource is used for managing links to internal
      accounts where the funds are managed by integrators.
    name: Internal Accounts
  - description: Requests to create and manage API keys
    name: API Keys
  - description: Requests to manage banks
    name: Banks
  - description: Requests to create and manage customers
    name: Customers
  - description: >
      A natural person (individual human) that is relevant to the Synctera
      platform in some way: e.g. a personal customer or a director/officer/owner
      of a business.
    name: Persons
  - description: >
      A legal entity (corporation, partnership, etc.) that is relevant to the
      Synctera platform in some way: a business customer or some other
      organization that has an ownership share in such a business customer.
    name: Businesses
  - description: >
      The fintech profile document resource is used to track the approval status
      of any documents

      which must be reviewed by a bank. This includes regulatory documents which
      will be presented

      to the fintech's end users, and also any documents that help the bank
      understand the

      fintech's fitness for duty.
    name: Fintech Profile
  - description: |
      The disclosures resource is used to track the status of disclosures and
      ensure that all parties have been shown the necessary disclosures to meet
      regulatory obligations.
    name: Disclosures
  - description: |
      The Disclosures resource is used to track the status of disclosures and
      ensure that customers have been shown the necessary disclosures to meet
      regulatory obligations.
    name: Disclosures (deprecated)
  - description: |
      The External Account resource is used for managing links to accounts
      that operate outside of the Synctera ecosystem.
    name: External Accounts
  - description: History
    name: History
  - description: Requests to initiate customer verification.
    name: KYC Verification (deprecated)
  - description: Requests to initiate customer verification.
    name: KYC/KYB Verifications
  - description: Requests to screen parties against sanctions watchlists
    name: Sanctions Screening
  - description: Requests to manage monitoring subscriptions and alerts for customers.
    name: Monitoring
  - description: Requests to manage partners
    name: Partners
  - description: Request to create and manage party groups and party group members
    name: Party Groups
  - description: Requests to create and manage roles
    name: Roles
  - description: >
      Represents the relationships between parties. A relationship can exist
      between personal customers, business customers, or non-customer
      persons/organizations.
    name: Relationships
  - description: Request to create and manage users
    name: Users
  - description: Request to enroll, renew, or cancel watchlist monitors
    name: Watchlist (deprecated)
  - description: Retrieve user identity information
    name: Identity
  - description: Endpoints for modifying or fetching posting dates
    name: Posting Dates
  - description: Admin API for Middesk configuration using the tenants API keys.
    name: Middesk
  - description: Requests to search and manage compliance searches
    name: Compliance Searches
  - description: Requests to configure vendors.
    name: Vendor Configurations
  - description: Requests to create and manage notes
    name: Notes
  - description: >
      Represents the compliance rules that are used to verify certain kinds of
      money movement.
    name: Compliance Rules
  - description: Requests to create licenses
    name: Licenses
  - description: >-
      Used to configure bank accounts for which synctera accounts are considered
      a "subledger" to
    name: Bank Account
  - description: Requests to search financial institutions
    name: Institutions (Beta)
  - description: Requests to manage addresses
    name: Addresses
  - description: Requests to Admins to grant permissions to user
    name: Request Permissions
  - description: Manage contacts for bank and fintech partners
    name: Contacts
  - description: Requests to create and manage personal ID configurations
    name: Personal ID Configuration
  - description: >-
      Migration mappings associate resources from an old tenant identity with a
      new tenant identity.
    name: Migration Mappings
  - description: FDX authentication and data transfer using Plaid Core Exchange
    name: Plaid Core Exchange (beta)
  - description: Create and manage wire transfers
    name: Wires
  - description: Simulate receiving Wire transactions and returns
    name: Wire Transaction Simulations
  - description: >-
      Create and manage same currency and multi-currency international wire
      transfers
    name: International Wires (alpha)
  - description: Create and manage holds
    name: Hold
  - description: Create and manage transactions
    name: Transactions
  - description: Create and manage transactions
    name: Transactions (internal)
  - description: Create and manage scheduled transactions
    name: Scheduled Transactions (internal)
  - description: Create and manage spending controls
    name: Spend Controls
  - description: Create and manage tenant configurations
    name: Tenant Configs
  - description: Lookup merchant information
    name: Merchants
  - description: See balance history
    name: BalanceHistory
  - description: API for effective balances
    name: effective_balances
  - description: Transaction lines API
    name: transactions
  - description: Create and manage transactions
    name: Transactions (beta)
  - description: Create and manage spending controls
    name: Spend Controls (beta)
  - description: |
      Requests to create and manage fees
    name: Fees (beta)
  - description: |
      Requests to create and manage Rewards
    name: Rewards (beta)
  - description: Create and manage disputes
    name: Disputes
  - description: Create and manage tenant-level transaction limits
    name: Tenant Limits (beta)
  - description: |
      Requests to create and manage batch payments
    name: Batch Payments (alpha)
  - description: Manage negative balance processes
    name: Negative Balance
  - description: |
      Manage fee products and fee configs for automated fee collection
    name: Fee Products
  - description: |
      Manage reward products and reward configs for automated cashback rewards
    name: Reward Products
  - description: Requests for risk evaluation and decisioning
    name: Risk Evaluations
  - description: Requests for transaction risk detection
    name: Transaction risk
  - description: Configuration and management of transaction monitoring rules
    name: Transaction Monitoring
  - description: Request to create and manage statements
    name: Statements
  - description: Create and manage EFT Canada transfers
    name: EFT Canada (Beta)
  - description: Create and manage sweep configurations
    name: Configs
  - description: Create a credit application.
    name: Applications (beta)
  - description: Billing period summaries
    name: Billing Period Summaries
  - description: Customer Service Details for disputes and billing inquiries
    name: Customer Service Details
  - description: Billing rates
    name: Billing Rates
  - description: Rates
    name: Rates
  - description: Lending Config
    name: Lending Config
  - description: Manage credit disputes
    name: Credit Disputes
  - description: Payments related to lending accounts
    name: Payments
  - description: Tenant Config
    name: Tenant Config
  - description: Bank Delinquency Configuration
    name: Bank Delinquency Configuration
  - description: >-
      Per bank/partner account-type mapping to FFIEC collateral codes used for
      regulatory call report furnishment.
    name: Collateral Code Configuration
  - description: >-
      Rules that map a posted payment transaction (bank/partner + transaction
      attributes) to a regulatory payment code. NULL match columns act as
      wildcards.
    name: Payment Code Configuration
  - description: Autopay configuration management for lending accounts
    name: Autopay Configs
  - description: Autopay payment records for billing periods
    name: Autopays
  - description: Configuration for mapping LoanPro events to Payola transaction parameters
    name: LoanPro Transaction Event Config
  - description: Create and manage payments
    name: ACH
  - description: Simulate receiving ACH transactions and returns
    name: ACH Transaction Simulations
  - description: Requests to create and manage webhooks
    name: Webhooks
  - description: Configure vendor secrets for egress requests
    name: Egress Gateway Vendor Secret CRUD API
  - description: Configure webhook secrets for egress requests
    name: Egress Gateway Webhook Secret CRUD API
  - description: Request to create and manage deposits using remote deposit capture
    name: Remote Check Deposit
  - description: Request to create and manage rdc configurations
    name: RDC Config
  - description: Create and manage Synctera Pay templates
    name: SyncteraPay
  - description: Create and manage Cash Order and Cash Deposit transfers
    name: Cash Orders and Deposits (alpha)
  - description: Requests to generate simulated transactions
    name: Cash Transaction Simulations (alpha)
  - description: >-
      Testing endpoints to simulate in-store cash deposits. Available in sandbox
      environments only.
    name: In-Store Cash Deposit Simulations
  - description: Create and manage barcodes for in-store cash deposits
    name: In-Store Cash Deposits
paths:
  /payments/{payment_id}:
    summary: Payment by ID
    get:
      tags:
        - Payments
      summary: Get payment
      description: >
        > 🚧 Beta

        > This is a Beta endpoint. Feedback from the community is welcome. We
        may make breaking changes to this endpoint.


        Get a payment by ID.
      operationId: getPayment
      parameters:
        - $ref: '#/components/parameters/payment_id'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/payment'
          description: Payment details
        '401':
          $ref: '#/components/responses/unauthorized'
        '403':
          $ref: '#/components/responses/forbidden'
        '404':
          $ref: '#/components/responses/not_found'
        '500':
          $ref: '#/components/responses/internal_server_error'
components:
  parameters:
    payment_id:
      description: Payment ID
      example: 2d0f7601-ecc6-48b4-b82f-5d64fa84628b
      in: path
      name: payment_id
      required: true
      schema:
        format: uuid
        type: string
  schemas:
    payment:
      description: A one-time payment made against a lending account.
      properties:
        attempt_history:
          $ref: '#/components/schemas/autopay_attempt_history'
        creation_time:
          description: Timestamp when the payment was created
          example: '2024-01-15T10:30:00Z'
          format: date-time
          type: string
        current_amount:
          description: >
            The amount in cents associated with this payment. For PENDING
            payments this

            is the originally requested amount (payments are not capped at the
            current

            balance -- an intentional overpayment is honored). For EXECUTED
            payments this

            mirrors executed_amount.
          example: 5000
          format: int64
          type: integer
        description:
          description: Description for the payment
          example: Payment
          type: string
        effective_date:
          description: Date the payment was (or will be) made
          example: '2024-01-25'
          format: date
          type: string
        executed_amount:
          description: The amount in cents actually paid, once executed.
          example: 5000
          format: int64
          type: integer
        id:
          description: Unique identifier for the payment
          example: 2d0f7601-ecc6-48b4-b82f-5d64fa84628b
          format: uuid
          type: string
        last_updated_time:
          description: Timestamp when the payment was last updated
          example: '2024-01-15T10:30:00Z'
          format: date-time
          type: string
        lending_account_id:
          description: The lending account this payment was made against
          example: 7d943c51-e4ff-4e57-9558-08cab6b963c7
          format: uuid
          type: string
        payment_attributes:
          $ref: '#/components/schemas/autopay_payment_attributes'
        payment_configs:
          $ref: '#/components/schemas/autopay_payment_configs'
        status:
          $ref: '#/components/schemas/autopay_status'
        tenant:
          $ref: '#/components/schemas/tenant'
      required:
        - id
        - lending_account_id
        - payment_configs
        - effective_date
        - status
        - description
        - creation_time
        - last_updated_time
      type: object
    autopay_attempt_history:
      description: History of execution attempts for an autopay
      properties:
        attempts:
          description: List of execution attempts, ordered chronologically
          items:
            $ref: '#/components/schemas/autopay_attempt'
          type: array
      required:
        - attempts
      type: object
    autopay_payment_attributes:
      description: |
        Identifiers for the payment created by an autopay execution.
        Only one field will be populated depending on the payment method used.
      properties:
        ach_id:
          description: ACH transaction ID when payment method is "ach"
          example: 6a4b1045-cdd0-82f8-f26c-9e08ce28062f
          format: uuid
          type: string
        transaction_id:
          description: Internal transaction UUID when payment method is "internal_transfer"
          example: 7b5c2156-dee1-93a9-a37d-0f19df39173a
          format: uuid
          type: string
      type: object
    autopay_payment_configs:
      description: Payment method-specific configurations
      properties:
        ach:
          $ref: '#/components/schemas/ach_payment_config'
        internal_transfer:
          $ref: '#/components/schemas/internal_transfer_payment_config'
      type: object
    autopay_status:
      description: |
        Status of the autopay:
        - PENDING: Autopay is scheduled and waiting to be executed
        - EXECUTED: Autopay was successfully executed
        - SKIPPED: Autopay was skipped (e.g., no balance due)
        - FAILED: Autopay failed to execute
      enum:
        - PENDING
        - EXECUTED
        - SKIPPED
        - FAILED
      type: string
    tenant:
      properties:
        bank_id:
          description: Bank ID
          example: 6
          type: integer
        partner_id:
          description: Partner ID
          example: 6
          type: integer
      required:
        - bank_id
        - partner_id
      title: Tenant
      type: object
    error:
      description: Synctera error responses in API v1 implement a custom error schema.
      properties:
        code:
          description: >
            A machine-readable string that identifies the error for programmatic
            use.
          example: BAD_REQUEST_BODY
          type: string
        detail:
          description: |
            A human-readable string explaining this particular error.
          example: 'Missing required fields: first_name, dob'
          type: string
        status:
          description: HTTP status code for this response
          example: 400
          type: integer
      title: Synctera error response
      type: object
    autopay_attempt:
      description: A single attempt to execute an autopay
      properties:
        attempted_at:
          description: Timestamp when the attempt was made
          example: '2024-01-25T14:30:00Z'
          format: date-time
          type: string
        payment_attributes:
          $ref: '#/components/schemas/autopay_payment_attributes'
        reason:
          description: Reason for failure or skip (if applicable)
          example: Insufficient funds in payment source account
          type: string
        status:
          $ref: '#/components/schemas/autopay_attempt_status'
      required:
        - attempted_at
        - status
      type: object
    ach_payment_config:
      description: Configuration specific to ACH payment method
      properties:
        external_account_id:
          description: The external account ID to debit via ACH
          example: 8f5b4c62-f5a0-4e68-9669-19dbc7a74d8e
          format: uuid
          type: string
        is_same_day:
          description: Whether to send as same-day ACH (default false)
          example: true
          type: boolean
        sec_code:
          description: Standard Entry Class Code (WEB, CCD, or PPD). Default is WEB.
          enum:
            - WEB
            - CCD
            - PPD
          example: WEB
          type: string
      required:
        - external_account_id
      type: object
    internal_transfer_payment_config:
      description: Configuration specific to internal transfer payment method
      properties:
        source_account_id:
          description: The internal Synctera platform account ID to transfer funds from
          example: 8f5b4c62-f5a0-4e68-9669-19dbc7a74d8e
          format: uuid
          type: string
        subtype:
          description: >-
            Transaction subtype for the internal transfer (default
            "autopay_payment")
          example: autopay_payment
          type: string
      required:
        - source_account_id
      type: object
    autopay_attempt_status:
      description: >
        Status of an autopay attempt:

        - SUCCESS: The attempt succeeded and payment was initiated

        - FAILED: The attempt failed (e.g., insufficient funds, validation
        error)

        - SKIPPED: The attempt was skipped (e.g., no balance due, already paid)
      enum:
        - SUCCESS
        - FAILED
        - SKIPPED
      type: string
  responses:
    unauthorized:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/error'
      description: Unauthorized
    forbidden:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/error'
      description: Forbidden
    not_found:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/error'
      description: Resource not found
    internal_server_error:
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/error'
      description: Internal server error
  securitySchemes:
    bearerAuth:
      bearerFormat: api_key
      scheme: bearer
      type: http

````