---
swagger: "2.0"
info:
title: SERV-PYI-D-PaymentFileManagement
description: this microservice contains the functionality for management of remote
authorization of the payment files
version: 1.0.0
x-ibm-name: serv-pyi-d-paymentfilemanagement
host: 127.0.0.1
schemes:
- https
basePath: /api
produces:
- application/json
paths:
/v1/servicing/payments/files/authorization:
post:
tags:
- remote-authorization
operationId: remote-authorization
summary: API to receive the authorization of the payment files
description: Receive the authorization of the payment files
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: 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: ChannelId
in: header
required: true
type: string
description: Channel where request originated
- name: sid
in: header
required: true
type: string
description: SessionId sent by Consumer
- name: remoteAuthorizationRequest
in: body
required: true
schema:
$ref: '#/definitions/RemoteAuthorizationRequest'
responses:
200:
description: Successful operation.
schema:
$ref: '#/definitions/RemoteAuthorizationResponse'
400:
description:
Type | Code | Details |
error | invalidRequest | Missing
or invalid Parameters |
schema:
$ref: '#/definitions/ErrorResponse'
401:
description: Type | Code | Details |
error | unAuthorized | Authorization
credentials are missing or invalid |
schema:
$ref: '#/definitions/ErrorResponse'
403:
description: Type | Code | Details | More
Info |
error | accessNotConfigured | The request
operation is not configured to access this resource | Channel/Country/Business
provided in the request is not supported currently |
schema:
$ref: '#/definitions/ErrorResponse'
404:
description: Type | Code | Details | More
Info |
error | resourceNotFound | The requested
resource was not found | Empty resource/resource not found |
schema:
$ref: '#/definitions/ErrorResponse'
422:
description: Type | Code | Details |
error | businessValidationFailed | Business
validation error occured on one or more parameters |
schema:
$ref: '#/definitions/ErrorResponse'
500:
description: Type | Code | Details |
fatal | serverUnavailable | The
request failed due to an internal error/server unavailability |
schema:
$ref: '#/definitions/ErrorResponse'
definitions:
RemoteAuthorizationRequest:
type: object
properties:
customerId:
description: CitiBanamex internal customer identifier
type: string
minLength: 1
maxLength: 12
pattern: ^[0-9]{1,12}
example: "887779"
checkerLegalRepresentativeId:
description: Representative of the Enterprise who review the file and give
confirmation
type: string
example: "99"
maxLength: 2
paymentFile:
$ref: '#/definitions/PaymentFile'
required:
- customerId
- checkerLegalRepresentativeId
- paymentFile
RemoteAuthorizationResponse:
type: object
properties:
transferReferenceNumber:
description: Unique identification number of confirmation of receipt of the
authorization request for a payroll file previously sent by another representative
type: string
example: "6412342"
required:
- transferReferenceNumber
PaymentFile:
type: object
properties:
paymentDate:
description: Date payment was requested
type: string
format: date
pattern: ([12]\d{3}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01]))
example: "2019-11-05"
fileSequenceNumber:
description: Customer file sequence number
type: integer
format: int32
example: 10
default: 0
required:
- paymentDate
- fileSequenceNumber
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://sandbox.externalapib2b.wlb.nam.nsroot.net:7101/mx-gcgapi-uat/sandbox2/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://sandbox.externalapib2b.wlb.nam.nsroot.net:7101/mx-gcgapi-uat/sandbox2
type:
- production
- development
...