Get pull transactions

GET /api/PullTransaction

Use this call to get past pull transactions. You can add query parameters to narrow down the search results.

Query parameters

Parameter

Description

cardToken
string

Card token for the debit card signed-up.
Optional

statusEnum
string

Status of the transaction:
0 - Pending
1 - Succeeded
2 - Failed
3 - Rejected
Optional

requesterId
string

Merchant ID.
Optional

fromDate
date/time

The starting date for the report.
Optional

toDate
date/time

The ending date for the report.
Optional

pageNumber
integer

The current page number determined by the total number of transactions and the number of transactions per page.

pageSize
integer

Number of transactions to list on a page.

Sample request GET /api/PullTransaction

curl -X GET
'https://pullfromcardapistg.crbnj.net/api/PullTransaction'
--header 'Accept: application/json'
--header 'Authorization: Bearer {xxx}'

Response attributes

Attribute

Description

transactionRequestId
*GUID

Unique customer generated transaction identifier.

amount
integer

Transaction amount in cents.

transactionRequestedAt
string

Date and time the transaction was requested.

transactionStatus
string

Status of the transaction:

  • Succeeded
  • Pending
  • Failed
  • Rejected

errorDescription
string

Description of any error that might have occurred.

creditCardId
string

Card token of the signed-up debit card.

railId
string

The processor used to perform the transaction

  • RS2
  • McSend
  • TabaPay

network
string

Card network.

  • Visa
  • Mastercard
  • ET
  • PULSE
  • STAR
  • NYCE
  • Accel
  • RPPS
  • MoneySend

retrievalReferenceId
GUID

Unique tracking identifier for this transaction in the processors to correlate this transaction to the processors.

actualTransactionDoneAt
string

Actual time the transaction was sent to the processor.

requestApproved
boolean

True if the payment passed all the way to the processor successfully, otherwise false.

responseReceived
boolean

True if P2P received a response from the external processor, otherwise false.

responseCode
string

An ISO 8583 two-digit code signifying the transaction result. For example, 00 means successful.

responseDescription
string

An ISO 8583 string description of the transaction result. For example, Approved.

traceNumber
string

Unique number that is assigned to a transaction when it leaves the merchant bank until it arrives at the cardholder bank.

error
string

Descriptive error, if relevant.

requesterName
string

Merchant name.

requesterMcc
string

Merchant Category Code (MCC).
4-digits that a credit card issuer uses to categorize consumer transactions for their card.

Sample response GET /api/PullTransaction

{
 "results": [
      {
        "transactionRequestId": "00000000-0000-0130-0000-000000000000",
        "amount": 400,
        "transactionRequestedAt": "2021-08-03T21:09:13.5882004",
        "transactionStatus": "Succeeded",
        "errorDescription": "null",
        "creditCardId": "KR7D47MNJIL2R39OZNRVPC0DIS82ES8JE6J7VU",
        "railId": "TabaPay",
        "network": "MasterCard",
        "retrievalReferenceId": "8abcb1fa-51f1-4b2d-9998-5948877bdcc0",
        "actualTransactionDoneAt": "2021-08-03T21:09:13.937",
        "requestApproved": true,
        "responseReceived": true,
        "responseCode": "00",
        "responseDescription": "Approved",
        "traceNumber": "00000000-0000-0130-0000-000000000000",
        "error": null,
        "requesterName": "Cooks",
        "requesterMcc": "8742"
      },
}

Did this page help you?