---
swagger: "2.0"
info:
  title: paym-pyo-v-codi-transaction-data
  description: This microservice is used to save the information of transactions from
    CoDi, to be reviewed in future audits.
  version: 1.0.0
  x-ibm-name: paym-pyo-v-codi-transaction-data
host: 127.0.0.1
schemes:
- https
basePath: /api
produces:
- application/json
paths:
  /v1/payments/codi-banxico/transactions-data/info:
    post:
      tags:
      - save-codi-transaction-data-info
      operationId: save-codi-transaction-data-info
      summary: 'LOB: Traditional Payments, Feature: Codi Transactions, Functionality:
        Save the information.'
      description: 'This API is used for save the information of transactions made
        in CoDi: B2B, SPEI and refunds.'
      consumes:
      - application/json
      produces:
      - application/json
      parameters:
      - name: client_id
        in: header
        required: true
        type: string
        description: Client ID generated during application registration
      - name: Authorization
        in: header
        required: true
        type: string
        description: The Authorization Token received during login
      - name: Accept
        in: header
        required: true
        type: string
        description: Content-Types that are acceptable for the response
      - name: uuid
        in: header
        required: true
        type: string
        description: 128 bit UUID that you generate for every request
      - name: Accept-Language
        in: header
        required: false
        type: string
        description: List of acceptable human languages for response
      - name: Content-Type
        in: header
        required: true
        type: string
        description: Content-Types that are sent in the request
      - name: ChannelId
        in: header
        required: true
        type: string
        description: Channel where request originated
      - name: countryCode
        in: header
        required: true
        type: string
        description: Country code in 2 character ISO 3166 format
      - name: businessCode
        in: header
        required: true
        type: string
        description: Business code identified during application registration
      - name: sid
        in: header
        required: true
        type: string
        description: SessionId sent by Consumer
      - name: saveCodiTransactionDataRequest
        in: body
        schema:
          $ref: '#/definitions/SaveCodiTransactionDataRequest'
      responses:
        204:
          description: Successful operation.
        400:
          description: <table><table><tr><td>Type</td><td>Code</td><td>Details</td></tr><tr><td>error</td><td>invalidRequest</td><td>Missing
            or invalid Parameters</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
        401:
          description: <table><tr><td>Type</td><td>Code</td><td>Details</td></tr><tr><td>error</td><td>unAuthorized</td><td>Authorization
            credentials are missing or invalid</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
        403:
          description: <table><tr><td>Type</td><td>Code</td><td>Details</td><td>More
            Info</td></tr><tr><td>error</td><td>accessNotConfigured</td><td>The request
            operation is not configured to access this resource</td><td>Channel/Country/Business
            provided in the request is not supported currently</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
        404:
          description: <table><tr><td>Type</td><td>Code</td><td>Details</td><td>More
            Info</td></tr><tr><td>error</td><td>resourceNotFound</td><td>The requested
            resource was not found</td><td>Empty resource/resource not found</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
        422:
          description: <table><table><tr><td>Type</td><td>Code</td><td>Details</td></tr><tr><td>error</td><td>businessValidationFailed</td><td>Business
            validation error occured on one or more parameters</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
        500:
          description: <table><tr><td>Type</td><td>Code</td><td>Details</td></tr><tr><td>fatal</td><td>serverUnavailable</td><td>The
            request failed due to an internal error/server unavailability</td></tr></table>
          schema:
            $ref: '#/definitions/ErrorResponse'
definitions:
  SaveCodiTransactionDataRequest:
    type: object
    properties:
      transaction:
        $ref: '#/definitions/Transaction'
      operation:
        $ref: '#/definitions/Operation'
    required:
    - transaction
    - operation
  Operation:
    type: object
    properties:
      responseOperationCode:
        description: Response code of the transaction already processed in Banxico.
        type: integer
        format: int32
        example: 200
      responseOperationDescription:
        description: Description response code of the transaction already processed
          in Banxico
        type: string
        example: OK
    required:
    - responseOperationCode
    - responseOperationDescription
  Transaction:
    type: object
    properties:
      transactionDate:
        description: Refers to the system date when the actual transaction was executed
          for an account.
        type: string
        format: date-time
        example: "2017-07-21T17:32:28Z"
      tokenType:
        description: The type of token requested for this digitization.
        type: string
        example: Hardtoken
      codiTransactionId:
        description: Transaction CODI ID refers to an identifier or code which uniquely
          identifies.
        type: string
        example: "12345678"
      paymentTypeCode:
        description: This attrbute indicates the payment type associated with the
          transaction
        type: string
        example: "19"
      transactionType:
        description: Refers to the type of transaction.
        type: string
        example: Payment B2B
    required:
    - transactionDate
    - tokenType
    - codiTransactionId
    - paymentTypeCode
    - transactionType
  ErrorResponse:
    properties:
      type:
        type: string
        description: Invalid - Request did not confirm to the specification and was
          unprocessed and rejected. Please fix the value and try again
        enum:
        - error
        - warn
        - invalid
        - fatal
      code:
        description: Error code which qualifies the error
        type: string
      details:
        description: Human readable explanation specific to the occurrence of the
          problem
        type: string
      location:
        description: The name of the field that resulted in the error
        type: string
      moreInfo:
        description: More Info can be used to pass any additional details
        type: string
      uuid:
        description: 128 bit UUID that you generate for every request
        type: string
      timestamp:
        description: Timestamp of the error
        type: string
    required:
    - type
    - code
x-ibm-configuration:
  enforced: true
  testable: true
  phase: realized
securityDefinitions:
  OAuth2 Application Flow:
    type: oauth2
    description: ""
    flow: application
    scopes:
      /api/v1: ""
    tokenUrl: https://sit.api.banamex.com/mx-gcgapi/sit/api/v1/oauth/token
  Client ID:
    type: apiKey
    description: ""
    in: header
    name: X-IBM-Client-Id
security:
- OAuth2 Application Flow:
  - /api/v1
  Client ID: []
x-ibm-endpoints:
- endpointUrl: https://sit.api.banamex.com/mx-gcgapi/sit
  description: Custom Gateway API Endpoint
  type:
  - production
  - development
...