Get SPI payment details

post

/bi/v1/{orgIdentifier}/getSPIPaymentDetails

First Available Version: 20.1.11

The API gets credit card payment transaction records for the given business date and location. This API returns data for customer who are using the Simphony Payment Interface (SPI). It does not return data for customers of Oracle MICROS Payment Cloud Service.

Request

Path Parameters
Body ()
The request body defines the details of the API request.
Root Schema : spiPaymentDetailsrequestPayload
Type: object
Request payload for SPI payment details
Show Source
Back to Top

Response

Supported Media Types

200 Response

OK
Body ()
Root Schema : spiPaymentDetails
Type: object
The response body contains information about the SPI payment details for the specified location and business date after a given date time.
Show Source
Nested Schema : revenueCenters
Type: array
An array of revenue centers
Show Source
Nested Schema : spiPaymentDetailsRVC
Type: object
The response body contains SPI payment transactions associated with a revenue center
Show Source
Nested Schema : transactions
Type: array
An array of credit card transactions in the revenue center
Show Source
Nested Schema : spiPaymentDetail
Type: object
The response body contains SPI payment transactions associated with a revenue center
Show Source
  • Title: Payemnt transaction amount
    Transaction amount of the payment
  • Title: Authorization Code
    Maximum Length: 30
    Authorization Code of the payment transaction, issues by Payment Service Provider (PSP)
  • Title: Payment card alias
    Maximum Length: 64
    A value that can be used to uniquely identify the payment card used. It cannot be used for card payments.
  • Title: Is card present
    Boolean flag indicating if the card was present while making the payment
  • Title: Check Number
    Maximum Length: 8
    Check Number
  • Title: Employee number
    Maximum Length: 16
    Employee number of the transaction employee, can be used to lookup from getEmployeeDimensions
  • Title: Entry mode number
    Return a numeric representation of the entry mode of the payment transaction. Following are possible values and their description:

    Entry Mode Enumeration:
    Entry ModeEntry Mode Description
    0EMV Fallback
    1Swiping without PIN (Backwards compatibility 6.1)
    2Manual enter card number (Backwards compatibility 6.1)
    3Swiping with PIN (Backwards compatibility 6.1)
    4EMV without PIN (Backwards compatibility 6.1)
    5EMV with offline PIN (Backwards compatibility 6.1)
    6EMV with on line PIN (Backwards compatibility 6.1)
    7Proximity via Magnetic Stripe (Backwards compatibility 6.1)
    8Proximity via ICC
    9Others
    10EMV Fallback (Signature Verification)
    11Proximity via Magnetic Stripe (Signature Verification)
    12Proximity via Magnetic Stripe (No CVM)
    13Proximity via ICC (Signature Verification)
    14Proximity via ICC (PIN Verification)
    15Proximity via ICC (Customer Device Verified)
    16Proximity via ICC (No CVM)
    17Swiping without PIN (Signature Verification)
    18Swiping with PIN (PIN Verification)
    19Swiping (No CVM )
    20Manual enter card number (Signature Verification)
    21Manual enter card number (No CVM)
    22EMV (Signature Verification)
    23EMV (PIN Verification)
    24EMV (PIN & Signature Verification)
    25EMV (No CVM)
    26E-Wallet Payment
    27Saved Card Token (No CVM)
  • Title: Guest Check identifier
    Maximum Length: 16
    Unique identifier of the Guest Check
  • Title: Guest check Line item identifier
    Maximum Length: 16
    Unique identifier of the Guest Check Line item
  • Title: Is offline flag
    Flag maintained to identify offline status
  • Title: Type of the payment
    Maximum Length: 30
    Type of the payment. Possible values: PAY, VOID, CANCEL, REFUND, ADJUSTMENT
  • Title: Reference identifying the transaction
    Maximum Length: 64
    Reference identifying the transaction, issued by Payment Service Provider (PSP)
  • Title: Retrieval Reference Number
    Retrieval Reference Number, issued by Payment Service Provider
  • Title: Transaction identifier
    Maximum Length: 12
    Unique transaction identifier issued by Simphony Payment Interface (SPI)
  • Title: Payment Terminal Identifier
    Maximum Length: 99
    Payment Terminal Identifier issued by Payment Service Provider (PSP)
  • Title: Tip amount
    Tip amount of the transaction. This attribute will not be returned in the response if value if null or zero.
  • Title: Tender media number
    Maximum Length: 16
    Tender media number, can be used to lookup from getTenderMediaDimensions
  • Title: The transaction date and time in local store timezone
    The transaction date and time in local store timezone
  • Title: The transaction date and time in UTC timzone
    The transaction date and time in UTC timzone
  • Title: Workstation number
    Maximum Length: 16
    Workstation number, can be used to lookup from getLocationDimensions

400 Response

Bad Request
Body ()
Root Schema : exceptionDetailType
Type: object
Error details
Show Source

401 Response

Unauthorized
Body ()
Root Schema : exceptionDetailType
Type: object
Error details
Show Source

403 Response

Service Unavailable
Body ()
Root Schema : exceptionDetailType
Type: object
Error details
Show Source

404 Response

Resource Not Found
Body ()
Root Schema : exceptionDetailType
Type: object
Error details
Show Source

Default Response

Unexpected Error
Body ()
Root Schema : exceptionDetailType
Type: object
Error details
Show Source
Back to Top

Examples

The following example shows how to get the payment detail for a specified location and business date after a given date time by submitting a POST request on the REST resource using cURL. For more information, see Use cURL

curl -i -X POST -H "Authorization: Bearer 
  
   " -H "Content-Type:application/json" -d {"locRef":"1234","busDt":"2020-10-20","changedSinceUTC":"2020-10-20T13:00:00"} https://baseurl/bi/v1/orgidentifier/getSPIPaymentDetails 
  

Example of Response Header

The following shows an example of the response header.

HTTP/1.1 200 OK  Date: Tue, 20 Oct 2020 21:24:33 GMT  Transfer-Encoding: chunked  Content-Type: application/json

Example of Response Body

The following example shows the contents of the response body in JSON format:

{
 "busDt": "2020-10-20",
 "locRef: "1234",
 "curUTC": "2020-10-20T14:00:00",
 "revenueCenters":[{
  "rvcNum": 123,
  "transactions":[{
   "pspRef": "VNV7FG58XCGMMM52",
   "chkNum": 7,
   "guestCheckID": 124563,
   "guestCheckLineItemId": 123,
   "amt":  123.45,
   "tip":  123.45,
   "transUTC": "2019-07-20T13:58:58",
   "transLcl": "2019-07-20T07:58:58",
   "pmntType": "PAY",
   "tmedNum": 15253,
   "seqNum": "670086133130",
   "wsNum": 1,
   "empNum": 12345,
   "terminalID": "P400Plus-804139629",
   "entryMode": 1,
   "cardPresentFlag": "true",
   "authCode": "03587B",
   "cardAlias": "76349057583904834AB",
   "offlineFlag": "true",
   "rrn": "SH5JZZ2GSM2J8HH2"
  }]
 }]
}
Back to Top