Firstoken API Docs
  • ⚙️API Reference
    • Firstoken API
      • Tokenization As A Service
        • Simple Tokenization
        • Simple Detokenization
        • Inspect Token
        • Delete Tokens
      • Transactions
        • Create a Transaction
        • Retrieve a Transaction
        • Inspect a Transaction
        • Delete a Transaction
        • Tokenize a Transaction
      • Proxy
        • Allowed Headers
        • Actions
        • Methods
          • POST - Proxy
          • GET - Proxy
          • PUT - Proxy
          • PATCH - Proxy
          • DELETE - Proxy
        • Get Payload Hash
        • Proxy JOSE
        • Proxy WSSEC
      • Inbound Routes
        • Create an Inbound - POST
      • Payments
        • Attributes of the Request
        • Common response
        • Endpoints
          • Authorizations
          • Reversals
          • Capture
            • Capture Refunds
            • Capture Void
          • Payments
            • Payment Refunds
            • Payment Void
          • Refunds void
          • Credit
            • Credit Void
          • Get Transaction Details
        • Decision Manager
          • How it works
          • Create decision
          • Update Decision
        • Risk Payer Authentication
          • How to use it
          • 3-D Secure Flows
            • Successful Frictionless Authentication
            • Unsuccessful Frictionless Authentication
            • Attempts Processing Frictionless Authentication
            • Unavailable Frictionless Authentication
            • Rejected Frictionless Authentication
            • Authentication not available on Lookup
            • Enrollment check error
            • Time-out
            • Bypassed Authentication
            • Successful Step-Up Authentication
            • Unsuccessful Step-Up Authentication
            • Unavailable Step-Up Authentication
            • Require Method URL
        • Point of Sale Payments
          • Authorization
          • Capture
          • Payment
          • Credit
  • 📖Guides
    • Firstoken Captures Hosted Iframe
      • How Firstoken Captures works
      • Generating a JSON Web Token
      • JSON form Schema
      • Iframe Communication
    • De-scoping Components
      • How Firstoken De-scoping Components works
      • Inbound Routes Module
        • Create an Inbound Route
        • Edit an Inbound Route
        • Delete an Inbound Route
      • Webhook Module
        • Create a Webhook
        • Edit a Webhook
        • Delete a Webhook
        • Webhook events
        • How to sign Webhooks data
      • Proxy Module
        • Create a Proxy
        • Edit a Proxy
        • Delete a Proxy
    • Firstoken Captures SDK JS
      • Getting Started
      • Functions
      • Type of Elements
      • Elements Options
      • CSS Object
      • Full Example of Usage
      • SDK versions
Powered by GitBook
On this page
  • Request Headers
  • Request Body
  • Response

Was this helpful?

  1. API Reference
  2. Firstoken API
  3. Payments
  4. Point of Sale Payments

Capture

This endpoint is used to capture a previously authorized payment transaction. It requires a JSON payload containing transaction details, capture information, and device information.

The URL for this endpoint is https://api.firstoken.co/v1/payments/:id/capture

In case of sandbox environment you should use this URL: https://api.firstoken-staging.co/v1/payments/:id/capture

Request Headers

  • Content-Type: application/json

  • x-api-key: <Your API Key>

id: string

The unique identifier of the transaction to be captured.

  • transaction_info: {object}

    • type Type of transaction. Possible values: capture.

    • reference_code Unique reference code for the transaction.

  • capture_info: {object}

    • amount_details

      • total_amount Total amount to be captured.

      • currency Currency code (e.g., MXN for Mexican Peso).

    • installments Number of installments for the capture.

  • device_info: {object}

    • ip_address IP address of the device making the request.

  • status Status of the response. Possible values: success, error.

  • message Message describing the result of the capture.

  • data {object}

    • transaction_info {object}

      • type Type of transaction response. Possible values: capture_response.

      • reference_code Unique reference code for the transaction.

      • transaction_id Unique transaction ID.

      • request_id Unique request ID.

      • status Status of the transaction. Possible values: Pending, Captured, Declined.

      • reconciliation_id Reconciliation ID for the transaction.

      • created_at Timestamp of when the transaction was created.

    • order_info {object}

      • amount_details {object}

        • total_amount Total amount captured.

        • currency Currency code.

Request Body

The request body should be a JSON object with the following structure:

Example of the JSON request
{
  "transaction_info": {
    "type": "capture",
    "reference_code": "123456789"
  },
  "capture_info": {
    "amount_details": {
      "total_amount": 1000,
      "currency": "MXN"
    },
    "installments": 1
  },
    "device_info": {
        "ip_address": "12.7.8.120"
    }
}

Response

The response will be a JSON object with the following structure:

Example of the JSON response
{
    "status": "success",
    "message": "Capture successful",
    "data": {
        "transaction_info": {
            "type": "capture_response",
            "reference_code": "123456789",
            "transaction_id": "0001733749102035492129",
            "request_id": "7337491022116075204953",
            "status": "Pending",
            "reconciliation_id": "hrklh3wWGoek",
            "created_at": "2024-12-09T12:58:22Z"
        },
        "order_info": {
            "amount_details": {
                "total_amount": "1000.00",
                "currency": "MXN"
            }
        }
    }
}

In case of an error, the response will have a status of fail and a descriptive message. The data object provides more details about the specific issues encountered.

PreviousAuthorizationNextPayment

Last updated 6 months ago

Was this helpful?

⚙️