Post Payment To Transaction Queue

Posts payment transaction data to the transaction queue for processing. This endpoint is used by payment processors to submit transaction information.

Endpoint: POST /post_to_transaction_queue

Request Parameters

ParameterTypeRequiredDescription
payment_identifierstringYesUnique identifier for the payment transaction
payment_amountfloatYesTotal payment amount
net_payment_amountfloatYesNet payment amount after fees
payment_typestringYesType of payment (ach, apple_pay, cash, cash_app, credit, debit, google_pay, paypal, pin4, venmo)
statusstringYesPayment status ("payment" for successful, "decline" for failed)
payment_timestampstringYesISO timestamp of the payment
site_order_identifierstringYesLending account number
processor_typestringYesPayment processor name (e.g., "BlytzPay")
order_identifierstringNoOrder identifier from the payment processor
processing_feefloatNoProcessing fee charged by the payment processor
withheld_amountfloatNoAmount withheld by the payment processor
site_customer_identifierstringNoCustomer identifier in the system
status_reasonstringNoReason for decline if status is "decline"
custom_fieldsobjectNoCustom fields as key-value pairs

Payment Types

  • ach - Automated Clearing House

  • apple_pay - Apple Pay

  • cash - Cash payment

  • cash_app - Cash App

  • credit - Credit card

  • debit - Debit card

  • google_pay - Google Pay

  • paypal - PayPal

  • pin4 - PIN-based debit

  • venmo - Venmo

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Request Body

  • The request body contains payment transaction details that are posted to the transaction processing queue.

Payment Types

  • ach — Automated Clearing House
  • apple_pay — Apple Pay
  • cash — Cash payment
  • cash_app — Cash App
  • credit — Credit card
  • debit — Debit card
  • google_pay — Google Pay
  • paypal — PayPal
  • pin4 — PIN-based debit
  • venmo — Venmo

Response Structure

  • Indicates whether the transaction was successfully added to the queue or already exists.
  • Returns the unique transaction identifier when applicable.

Example Response

{
    "message": {
        "success": true,
        "message": "Transaction already exists in queue",
        "transaction_id": "BLY-123456789"
    }
}
Body Params
string
required

Unique identifier for the payment transaction

float
required

Total payment amount

float
required

Net payment amount after fees

string
required

Type of payment (ach, apple_pay, cash, cash_app, credit, debit, google_pay, paypal, pin4, venmo)

string
required

Payment status ("payment" for successful, "decline" for failed)

string
required
Defaults to ISO timestamp of the payment
string
required

Lending account number

string
required

Payment processor name (e.g., "BlytzPay")

string

Order identifier from the payment processor

float

Processing fee charged by the payment processor

float

Amount withheld by the payment processor

string

Customer identifier in the system

string

Reason for decline if status is "decline"

string

Custom fields as key-value pairs

Response

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!