Payment types

Bond Studio supports card, ACHACH - Automated Clearing House. The network that coordinates electronic payments and automated money transfers., and account payment types.

The transaction object contains a details object that contains the payment details. The three payment types require different sets of attributes in the details object.

For transaction type details, see Transaction types.

Card payments

The following code sample extract displays the attributes of a details object for a card transaction.

{
"details": {
    "card_id": "c5326b94-73f2-427d-b8cb-4605519da842",
    "mcc": "3542",
    "mcc_description": "Professional Services and Membership Organizations",
    "currency": "USD",
    "exchange_rate": "0.00",
    "merchant_id": "1AD18GT7744554",
    "merchant_name": "Target",
    "merchant_city": "San Mateo",
    "merchant_state": "CA",
    "merchant_country": "USA",
    "merchant_postal_code": "90210",
    "cardholder_presence": true,
    "statement_descriptor": "Target #4744",
    "arn": "000091556011",
    "fraud_rule_triggered": "spend_velocity"
        }
}

The following table describes the details attributes for a card transaction.

Attribute

Description

card_id

UUID for the card.

mcc

Numeric value for the merchant category code. For details, see MCC Codes and Descriptions.

mcc_description

Descriptions for the merchant category code. For details, see MCC Codes and Descriptions.

currency

Currency the transaction was processed in.

exchange_rate

Exchange rate, if applicable.

merchant_id

Unique identifier for the merchant.

merchant_name

Name of the merchant.

merchant_city

City the merchant resides in.

merchant_state

State the merchant resides in.

merchant_country

Country the merchant resides in.

merchant_postal_code

Zip or postal code for the merchant.

cardholder_presence

  • `true` if the cardholder was present when the card was swiped.
  • `false` if the cardholder was present when the card was swiped.

statement_descriptor

Describes the transaction.

arn

ARN, also called the Trace ID. Tracks a debit or credit transaction from the merchant's bank to the card holder's bank

fraud_rule_triggered

Identifies the fraud rule, if any, for this transaction.

ACH payments

The following code sample extract displays the attributes of a details object for an ACH transaction.

{
"details": {
      "card_id": "c5326b94-73f2-427d-b8cb-4605519da842",
      "external_account_id": "51fca76f-60a0-4db1-a0b7-d98a3687fa42",
      "class_code": "WEB",
      "direction": "credit",
      "network": "same-day-ach",
      "description": "PAYROLL",
      "failure_reason": "Insufficient Funds",
      "return_code": "R01"
      }
}

The following table describes the details attributes for an ACH transaction.

Attribute

Description

card_id

The unique identifier for the card.

external_account_id

The ID of the external account linked in the ACH transfer.

class_code

A three-letter code identified by NACHA standards. See ACH Class Codes for details.

direction

credit or debit. Defines the direction of the transaction.

network

ach or same-day-ach.

description

A 10 character description that you can include.

failure_reason

Reason for the ACH failure.

return_code

The return code defined by NACHA standards. For details, see ACH Return Codes.

Account payments

Account payments are also know as card-to-card payments.

The following code sample extract displays the attributes of a details object for an card-to-card transaction.

{
"details": {
    "origination_card_id": "2742ff6a-7455-4066-8b45-ae12d3acca34",
    "destination_card_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
        }
 }

The following table describes the details attributes for an RDC transaction.

Attribute

Description

origination_card_id

card_id which originated the transaction.

destination_card_id

Destination card_id for the transaction.


Did this page help you?