Migrate authorizations

post

https://gw-pci.pismolabs.io/migrations/v1/migrations/authorizations

Start authorizations migration.

This endpoint generates the following events:

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Start migration of authorizations

acquirer_bin

string

required

Authorization acquirer BIN

arqc_presence

boolean

required

Is authorization ARQC (Authorization Request Cryptogram) present?

authorization_code

string

required

Authorization code generated for this operation (6 alphanumeric characters, DE 38).

authorization_response_code

string

required

Response code of the authorization (DE 39), such as 00 (Approved) or 51 (Insufficient Funds). This value must be a valid code for the card network.

authorization_status

string

enum

required

Authorization status

PENDING—Authorizations from Base I pending confirmation
PROCESSED—Base II confirmation
DROPPED—Authorization discarded if the confirmation (Base II confirmation) is not received within 10 days.
DECLINED—Authorization denied when the validation fails (response code <> 00).
CANCELED—Canceled authorization For information about clearing (Base II) and Base I authorization, refer to Clearing/base II.

Allowed:

contract_amount

number

required

Total authorization amount with fees

currency_conversion_date

string

required

Authorization currency conversion date. Format = YYYY-MM-DDTHH:mm:ssZ.

cvv_presence

boolean

required

Is authorization CVV present?

entry_mode

string

required

Authorization entry mode (such as 05 - Manual entry or 02 - Magnetic stripe read).

event_date_hour

string

required

Local authorization date and time according to value received in flag message (DE 12 and 13 + year). Pismo accepts this value but does not adjust for time zones in reporting or other uses. To order authorizations chronologically, use event_date_hour_utc. UTC (Coordinated Universal Time) simplifies comparisons for settlement, SLA tracking, and reporting, and prevents mismatches caused by local offsets. Format = YYYY-MM-DDTHH:MM:SS.

event_date_hour_utc

string

required

Authorization event UTC date and time. UTC (Coordinated Universal Time) simplifies comparisons for settlement, SLA tracking, and reporting, and prevents mismatches caused by local offsets. Format = YYYY-MM-DDTHH:MM:SSZ.

local_amount

number

required

Local currency value (DE 04), indicating the amount the cardholder requested in the acquirer's local currency or the transaction's source location.

local_currency_code

string

required

Local ISO-4217 currency code (DE 49)

merchant_city

string

required

length ≤ 15

Authorization merchant city (DE 43 city field, maximum 15 characters)

merchant_name

string

required

Authorization merchant name

merchant_state_or_country

string

required

length ≤ 2

Authorization merchant state or country using ISO 3166-1 alpha-2 country code

migration

object

required

Applicant additional migration information

mti

string

enum

required

Authorization ISO 8583 MTI (message type indicator): 0100—Purchase 0120—Purchase advice 0200—Debit purchase 0400—Cancellation 0420—Cancellation advice

Allowed:

network

string

enum

required

Brand (such as Visa or Mastercard)

Allowed:

nsu

string

required

length ≤ 6

Provides a DE Field 11 value that a message initiator assigns to uniquely identify a transaction as NSU or STAN:

NSU (Network Settlement Utility) tracks the flow of funds between parties involved in a payment card transaction. Different payment card networks could have their own NSU systems. For example, Visa has VisaNet, Mastercard has BankNet, or the payment network could have a third-party network.
STAN (System Trace Audit Number) is a number (DE Field 11) that the message initiator assigns to uniquely identify a transaction.

pin_presence

boolean

required

Is authorization PIN present?

postings

object

required

Posting metadata (key-value pairs) that accepts any value. Maximum size is 1000 bytes.

principal_amount

number

required

Total authorization amount, not including fees

processing_code

string

required

Authorization processing code (custom alphanumeric identifier that defines how the Pismo platform handles a certain financial operation type).

Processing codes are integral to the transactions flow on the Pismo platform. The platform uses predefined processing codes to evaluate and process operations. For more information, refer to Processing codes and transaction types.

Note: This processing code may not exactly match the DE03 (subfield 1) message from Visa, Mastercard or any other network. example: "00"

retrieval_reference_number

string

required

Authorization retrieval reference number received in flag message (DE 37)

settlement_amount

number

required

Settlement currency amount (DE 05, destination amount). Indicates the amount transferred between the acquirer and the issuer equal to DE 04 (amount, transaction) in the settlement currency. Mastercard programs and services use U.S. dollars as the currency of settlement.

settlement_currency_code

string

required

Authorization settlement currency code

track1_presence

boolean

required

Is authorization magnetic stripe Track 1 data present?

track2_presence

boolean

required

Is authorization magnetic stripe Track 2 data present?

transaction_identifier

string

required

Unique transaction ID (refer to DE 63 for Mastercard, DE 62.2 for Visa).

Note: This field is critical for doing network reconciliations post migration. If you are migrating pending authorizations and you don't have this field, contact your Pismo representative for guidance.

update_limit

boolean

required

Defaults to false

Should the authorization affect the account's credit limit?

Note: This should only be true in specific scenarios. Before you enable this option, contact your Pismo representative for guidance.

cardholder_amount

number

Transaction amount billed to the cardholder in the issuer's currency (DE 06 optional).

cardholder_currency_code

string

Cardholder currency code (DE 51, cardholder), in ISO 4217 numeric code format

cardholder_currency_conversion_rate

number

Conversion rate between local amount and cardholder amount (the DE 10 conversion rate that the brand sends)

installment_amount

number

Authorization installment amount

merchant_category_code

string

Authorization merchant category code (MCC), a four-digit ISO 18245 number

merchant_id

string

Authorization merchant ID

metadata

object

Authorization metadata (key-value pairs) that accepts any values except PCI data. Maximum size is 1000 bytes.

number_of_installments

integer

Defaults to 1

Total number of installments related to the authorization that is being migrated

pre_authorization

boolean

Is authorization a pre-authorization? On pending authorizations, this affects the time that it takes to cancel the authorization if no confirmation arrives from the network settlement file.

referral_updated_at

string

Date and time when the referral was last updated. Identifies when a fraud suspicion is no longer valid. Format = YYYY-MM-ddTHH:mm:ss.

settlement_currency_rate

string

Authorization settlement currency rate

terminal_capability

string

Is terminal pre-authorized? Field 130 (Visa) and DE 61 (Mastercard) POS (Point Of Sale). REQUIRED for chip purchases.

token_requestor_id

string

Authorization token requestor ID

wallet_identifier

string

Authorization wallet identifier

ledger_impact

array of strings

deprecated

Limits impacted by the ledger during the authorization.

Note: This is a legacy field. You should use the ledger_updates array instead.

ledger_impact

Responses

202

Accepted

Migrate authorizations

Changelog

Support

Pismo is here to help

400Bad request

500Internal error