API Reference

MoneySend API

post
https://uatmea-iss-apigw.creditpluspinelabs.com/deviceapi/apis/v1/services/transactions/crossBorderPayment

Pine Labs MoneySend is a set of Pine Labs Network transactions that facilitate both domestic and cross-border fundstransfer between Pine Labs branded cards(Consumer Cards and Eligible Small Business Commercial Card accounts, excluding anonymous prepaid and gift card accounts).

A Sender may be a Consumer, business, government, or non-profit organization while the Recipient is a Consumer or mobile money agent. This API can be used to by the sender to initiate a cross border funds transfer between P2P or P2B.

HTTP Status and Response Status Matrix

  • HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
  • Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
  • Reason: This is the description of the error code returned by Credit+ Issuing application.
  • Details: This is the detailed description of the error code returned by Credit+ Issuing application
HTTP CodeError CodeReasonDetails
201000Request processed successfully
400997Request Parameters Validation
401990Unauthorized access
404998Device(s) does not exist
500993Request processing error
400401User Or Bank does notsupport API
500TRANSACTION_PROCESSING_TIMEOUTThe transaction processing has got timed out. Please try after some time.A reversal entry would be created for the transaction only if the processing is successful.
500TRANSACTION_PROCESSING_FAILUREThe transaction cannot be processed. Please try after some time.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
enum
required
length ≤ 10
^[0-9]+$

Network code associated with the acquirer ID. Not NULL. Numeric only. Valid values: 31, 32, 33.

Allowed:
string
enum
required
length ≤ 1

Flag to enable the passCode. Not NULL. Valid values: Y (Enabled), N (Disabled).

Allowed:
string
length ≤ 200

Login and password of the acquirer ID, hashed with SHA5 algorithm. Must not be NULL if passCodeFlag is Y, otherwise NULL. Maximum length: 200.

string
enum
required
length ≤ 3

Identifies the value sent in formFactor. Not NULL. Only CRD (Card number) supported. Maximum length: 3.

Allowed:
string
required
length between 10 and 24

Card number of sender. Not NULL. Minimum length: 10. Maximum length: 24.

string
required
length ≤ 4
^[0-9]{4}$

Card expiry date. Not NULL. Format: YYMM. Maximum length: 4.

string
required
length between 12 and 12

Unique authorization reference number. Not NULL. Length: 12.

string
required
length between 6 and 6

Trace audit number assigned by the originator to uniquely identify a transaction. Not NULL. Length: 6.

string
required
length between 12 and 12
^[0-9]{12}$

Transaction date and time at acceptor location. Not NULL. Format: YYMMDDHHMMSS. Length: 12.

string
required
length between 12 and 12
^[0-9]{12}$

Channel transmission date and time in Coordinated Universal Time (UTC). Not NULL. Format: MMDDHHMMSS. Length: 12.

string
required
length ≤ 12
^[0-9]+$

Transaction amount decimalized as per currency exponent. Not NULL. Numeric. Must be greater than 0. Maximum length: 12.

string
required
length between 3 and 3
^[0-9]{3}$

Three-digit numeric ISO currency code. Not NULL. Length: 3.

string
required
length between 8 and 8

Card acceptor terminal identification code, as per ISO standard. Length: 8.

string
required
length between 15 and 15

Card acceptor identification code, as per ISO standard. Length: 15.

string
required
length between 40 and 99

Name and address of the card acceptor as per ISO standard. Minimum length: 40. Maximum length: 99.

string
required
length between 1 and 200

Uniform Resource Identifier (URI) uniquely identifying the sender’s account (e.g., phone number or email address). Minimum length: 1. Maximum length: 200. Supports special characters.

string
required
length between 1 and 200

Uniform Resource Identifier (URI) pointing to the beneficiary’s account. Minimum length: 1. Maximum length: 200. Supports special characters.

string
length between 3 and 3

Three-letter ISO 3166-1 alpha-3 country code of the country in which the payment is initiated. Length: 3.

string
required
length between 3 and 3

Three-letter ISO 4217 currency code of the recipient account. Length: 3.

string
length between 1 and 140

Name of the bank holding the recipient account. Required for specific bank service provider endpoints per corridor data. Supports special characters. Minimum length: 1. Maximum length: 140.

string
length between 1 and 30

Name of the bank branch holding the recipient account. Required for specific bank service provider endpoints per corridor data. Supports special characters. Minimum length: 1. Maximum length: 30.

string
length ≤ 140

Bank code associated with the bank name and BIC. Required for specific bank service provider endpoints per corridor data. Supports special characters. Maximum length: 140.

string
enum
required
length between 3 and 3

Type of transaction. Valid values: P2P (Person to Person), P2B (Person to Business). Length: 3.

Allowed:
string
length between 1 and 30

Sender’s identification of the source of funds. Required for specific receiving service provider endpoints per corridor data. Minimum length: 1. Maximum length: 30.

string
length between 1 and 40

Beneficiary’s first name for P2P transactions. Mandatory for P2P. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 40.

string
length between 1 and 40

Beneficiary’s middle name for P2P transactions. Optional. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 40.

string
length between 1 and 40

Beneficiary’s last name for P2P transactions. Mandatory for P2P. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 40.

string
length ≤ 200

Organization’s name for P2B transactions. Mandatory for P2B. Supports alphanumeric and special characters. Maximum length: 200.

string
required
length between 3 and 3

Three-letter ISO 3166-1 alpha-3 code for beneficiary’s nationality. For organizations, the registered country is used. Length: 3. Alphabets only.

string
required
length between 1 and 100

Address line 1 of the beneficiary. For businesses, the business address is used. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 100.

string
length between 1 and 100

Address line 2 of the beneficiary. For businesses, the business address is used. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 100.

string
required
length between 1 and 20

City of the beneficiary. For businesses, the business city is used. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 20.

string
required
length between 2 and 3

State or province of the beneficiary. For businesses, the business state/province is used. Use country code if no subdivision exists. Alphabets only. Minimum length: 2. Maximum length: 3.

string
length ≤ 10

Postal code of the beneficiary. For businesses, the business postal code is used. Mandatory if ZIP Code flag at Institution > Location Parameters is set. Supports alphanumeric and special characters. Maximum length: 10.

string
required
length between 3 and 3

Three-letter ISO 3166-1 alpha-3 code for beneficiary’s country. For businesses, the business country is used. Alphabets only. Length: 3.

string
length between 1 and 2000

Uniform Resource Identifier (URI) identifying the beneficiary’s government-issued ID. Supports alphanumeric and special characters. Minimum length: 1. Maximum length: 2000.

string
length ≤ 20
^[0-9]+$

Phone number of the beneficiary. For businesses, a contact’s phone number is used. Numeric only. Maximum length: 20.

string
length ≤ 254

Email address of the beneficiary. For businesses, a contact’s email is used. Supports alphanumeric characters. Maximum length: 254.

string
length between 1 and 30

Purpose of payment. Required for specific receiving service provider endpoints per corridor data. Supports alphanumeric characters. Minimum length: 1. Maximum length: 30.

Headers
string
^[a-zA-Z0-9-]{1,50}$

API Consumer must share Correlation-ID in HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate a universally unique identifier (UUID) of length 32 or 36 that is compliant with RFC 4122. The maximum supported length is 50 alphanumeric characters. For example, ac97d177-9345-4934-8343-0f91a7a02836. If the Correlation-ID is not received in the incoming request, the system generates the UUID dynamically and assigns it to the request.

string

API Consumer can share Source in HTTP header for API requests. For the list of Source values, see the Pre-conditions for HTTP Header of REST API topic in the Pre-requisite for Rest API section.

Response

Updated about 1 year ago

Did this page help you?
Language
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated about 1 year ago

Did this page help you?