1. Changelog

Version Date Description

9.7

2024-05-23

Added optional "rodo" and "marketing" flags for Add user USA or CAN transactions request 11.1.1. Add user, and Update user request 11.2.1. Update user

9.6

2024-04-16

Added new webhook notification occuring during CASH_ACCOUNT transaction processing.

9.5

2024-04-10

Added webhook : Acquirer reconciliation date webhook + Acquirer reconciliation date webhook

9.4

2024-04-06

New transaction model in Payouts area is released. Now we can process transaction from Card to Account number. New transaction model was added as new tab in Card to Card section: + New CARD-ACCOUNT transaction model + New CARD-ACCOUNT transaction model with 3DS

9.3

2024-04-05

New regexp for houseNumber

9.2

2024-04-05

Payouts from deposit Possibility to make payouts with tokens.

9.1

2024-02-15

Release of the new method Calculate commission payout. The method informs about the amount that will be removed from the deposit and gives possibility to use exact result in the send money method.

9.0

2023-12-29

Added new status to send-money methods: ERROR_WEEKLY_TRANSACTION_LIMIT. Adjustment of card limits for Visa and Mastercard organizations.

8.9

2023-12-14

New transaction model in Payouts area is released. Now we can process transaction from Deposit to Account number. Look here for more information and navigate to CASH-ACCOUNT tab in Request section + New CASH-ACCOUNT transaction model

8.8

2023-11-20

Adding information about Merchant Advice Codes. Changes in check transaction status response - new field merchantAdviceCode. Occurs only for Mastercard and for declined transactions if Mastercard returns this information

8.7

2023-11-02

Complete end of support for 3ds version 1.0

8.6

2023-10-26

Added new payment method BLIK-CARD BLIK to Card

8.5

2023-03-21

Added new optional fields for method /client/3ds/authentication regarding Cardholder Billing Information

8.4

2023-02-16

Regexp for house number properties in each occurrences was changed

8.3

2023-01-11

Following to the newest Mastercard Data Integrity Monitoring Program Edits for Funding Transactions all of the money transfers must contain additional informations about receiver: First name and Last name. Consequently delayed receiver type for delayed payment: Receiver Delayed was changed - required fields: firstName and lastName were added.

8.2

2022-12-02

Added new field to receiver - country of residence. Changes in request transactions - sender country is required for merchant crypto. Added new status to check status send-money response: ERROR_TRANSACTION_BLOCKED_WITH_CARD_ISSUED_IN_GIVEN_CARD_COUNTRY

8.1

2022-12-09

Extension of methods determine currency and currency for card by country card

8.0

2022-12-01

Delete field 'currency' from sender models: Sender Cash and Receiver Cash. Restrict 'type' field to specific transaction types: CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER

7.9

2022-11-24

Added new status to check status send-money response: MERCHANT_CRYPTO_OUTSIDE_EEA_UK_NOT_SUPPORTED

7.8

2022-11-07

Documentation enhancement, minor fixes and better details for 401 UNAUTHORIZED status

7.7

2022-10-26

Removal from use 3DS 1 for all countries (except those configured in the system)

7.6

2022-10-24

Adding information about the withdrawal of 3DSv1.

7.5

2022-10-13

New optional birthDay parameter added to Sender and Receiver data. This parameter may help in AML verification

7.4

2022-10-12

Changes in Payment of Delayed Transaction - now it is enabled to include cardId without plain card number in request, look at 4. Delayed payment chapter

7.3

2022-10-06

New statuses added for Delayed Payment: ERROR_SINGLE_TRANSACTION_LIMIT, ERROR_DAILY_TRANSACTION_LIMIT, ERROR_DAILY_COUNT_TRANSACTION_LIMIT, ERROR_MONTHLY_TRANSACTION_LIMIT, ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT, ERROR_DAILY_CUMULATIVE_LIMIT, ERROR_MONTHLY_CUMULATIVE_LIMIT, ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT, ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT, ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT, LIMIT_ERROR. Statuses may be occurred in Delayed Send Money and in Delayed Payment methods.

7.2

2022-10-03

Updated error responses in delayed send money / payment operations (card lock info added).

New endpoints added: + Check the detailed status of a multi-currency transaction + Check the detailed status of a 3DS transaction

7.1

2022-08-26

New status added for Delayed Payment feature: ERROR_DELAYED_PAYMENT_UNEXPECTED_EXCEPTION_OCCURRED

7.0

2022-08-05

New request field on 3DS 2.X: challengeWindowSize

6.9

2022-07-15

Added new fields Cardholder First Name and Last Name to Add card method. + 14.1. Add card

6.8

2022-06-13

Delete status ERROR_TRANSACTION_USER_NAME_CONTAINS_FRAUDULENT_PART, added a new INCORRECT_NAME_DATA status that will have the same role.

6.7

2022-05-09

Added new statuses to send-money methods: ERROR_TRANSACTION_USER_NAME_CONTAINS_FRAUDULENT_PART - Transaction rejected, sender or receiver name contains fraudulent phrase, ERROR_NAME_VERIFICATION - Transaction rejected, suspicious sender or receiver name

6.6

2022-04-14

Added new status to check status send-money response: ERROR_VALIDATION_EXPIRY_DATE

6.5

2022-04-08

Added new fields to check status method. Fields: merchantSettlementCurrency, fenigeCommissionInMerchantSettlementCurrency, transactionAmountInMerchantSettlementCurrency

6.4

2022-03-11

New transaction status added (MASTERCARD_MAC_TPE_EXCELLENCE_RULE) for all transactions type to reject transaction. Transaction rejected, when second transaction with merchant advice code 03 or 21 was retried within 30 days. + 3. Send money + 4. Delayed payment

6.3

2022-02-28

Added new field for Add Card method. It is possible to correlate Sender Card with phone number now. One phone number can hold one card per User. Additionally new status was added: ERROR_CARD_WITH_PHONE_NUMBER_EXISTS, when card with phone number exists for such User. + 14.1. Add Card

6.2

2022-03-10

Add new PLAIN-DATACORE methods. + 3. Send money + 8. Determine currency + 9. Calculate commission

6.1

2022-02-07

Add new response error statuses: ERROR_SINGLE_TRANSACTION_LIMIT, ERROR_DAILY_COUNT_TRANSACTION_LIMIT, ERROR_MONTHLY_TRANSACTION_LIMIT, ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT.

6.0

2022-01-15

Add new response error status: ERROR_TRANSACTION_PROCESSING_TIME_TOO_LONG + 3. Send money

5.9

2021-12-06

New transaction status added (ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED) for all transactions type to indicate blocked transaction in specific geographic scope + 3. Send money + 4. Delayed payment

5.8

2021-12-29

Add new API methods for reset user password + 13. User management

5.7

2021-12-10

Changed constraint from optional to required on country field in user management > add user.
Added new statuses INVALID_COUNTRY in Add user response and INVALID_COUNTRY_ID in Update user response.

5.6

2021-12-09

Documentation updated. Error ERROR_CARD_ALREADY_EXISTS_FOR_ANOTHER_USER added for add card error statuses.

5.5

2021-12-06

Updated validation for purchaseAmount in Authentication request in 3DS 2.X verification methods

5.4

2021-11-16

Added new mandatory field when country is set to US (United States) or CA (Canada) to CASH_PLAIN and CASH_PHONE send-money methods.

5.3

2021-11-08

Updated information about API-TOKEN refresh time in methods that require it

5.2

2021-10-27

Add new response error statuses: ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED, ERROR_FUNDING_CARD_COUNTRY_RESTRICTED, ERROR_MERCHANT_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED, ERROR_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED + 3. Send money + 4. Delayed payment

5.1

2021-10-25

Removed redundant validation response statuses from methods + Card to Card + Payouts on Card + Card to Card 3D Secure + The change does not affect the API.

5.0

2021-10-20

New status added for send-money validation error response: ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER 3. Send money

4.9

2021-10-14

Added new types: DOMESTIC_PL, INTRA_EU, INTER to geographicScope field in 9. Calculate commission

4.8

2021-10-05

Addition of an explanation of the default status ERROR_SOMETHING_WRONG for the check status send money methods + 3.1.3 Check status + 3.2.3 Check status

4.7

2021-09-06

New merchant cumulative limits added: daily and monthly cumulative limit for all card providers. + New Statuses added: ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT + 3.1.3 Check status + 3.2.3 Check status

4.6

2021-09-07

New response status ERROR_API_TOKEN_NOT_FOUND added when API-TOKEN header is not attached to DATACORE based request

4.5

2021-05-05

An implementation of CODE_65/CODE_1A transaction rejection logic for MASTERCARD and VISA. More details can be found here: 3. Send money 4. Delayed payment

4.4

2021-04-26

Introducing a service that validates the personal information of transaction users and Add User method data. In case of positive verification, the transaction/Add User is rejected with the status: ERROR_USER_VERIFICATION

4.3

2021-04-22

Exclusion of deprecated currencies. Validation will reject these currencies: BYR, LTL, MRO, RUR, STD

4.2

2021-03-01

Introduction of a new webhook functionality. Now it is possible to handle information about transaction status without polling API. + 5. Webhooks

4.1

2021-02-17

New status: CARD_MODIFY_LIMIT_REACHED for Add/Delete Card and Add/Delete Friend Card methods. Default limits are set to 3 cards modifications e.g. Add/Delete card per user during 24h also 3 modifications for friend cards. These values could be modified for the merchant, please contact us if you need changes.

4.0

2021-02-02

Added method Currency rate by provider which also allows you to download historical rates.

3.9

2021-02-02

Added new fields '3DS', 'amountInUsDollar', 'provider', 'bankName' on thw response body for Check status and Transaction history methods.

3.8

2021-01-18

New fields 'merchantUrl' and 'addressIp' in Send Money request added. Both fields are optional now, but it is recommended to include it in your request body. From 2021-05-03 the fields will be required.

3.7

2021-01-13

New merchant cumulative limits added: daily and monthly with distinction between Mastercard and VISA. + New Statuses added: ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT, ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT, ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT + Old status to remove: ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT + 3.1.3 Check status + 3.2.3 Check status 3ds

3.6

2021-01-05

Updates for 3DS 2.X

3.5

2020-12-16

Modify personal data validation for send money methods, especially sender and receiver - firstName, lastName, email. Set minimum length 2 for firstName and lastName. FirstName and lastName cannot be the same and cannot consist of the same characters. One email address cannot be the same within sender and receiver for 2 different personal data.

3.4

2020-12-03

Add new Delayed Payment methods. + 4. Delayed payment

3.3

2020-12-02

New status: CARD_LIMIT_REACHED for Add Card and Add Friend Card methods. Default limits are 5 cards per user and 5 friend cards per user. These values are configured for the merchant, please contact us if you need changes

3.2

2020-11-17

3DS 2.x method introduced in Send money + Card to Card 3D Secure

3.1

2020-10-14

Add new VISA response code value 80

3.0

2020-10-05

Documentation updated. Error CURRENCY_RATES_NOT_FOUND added for send money error statuses.

2.9

2020-07-09

Description of check card’s provided added.

2.8

2020-07-03

Documentation updated. Error ERROR_WHILE_GETTING_COUNTRY_CODE added for Calculate commission method.

2.7

2020-06-03

Documentation updated. Change value and description about field "md" in Initialize and Finalize methods: + 5.2. Initialize + 5.3. Finalize

2.6

2020-05-21

User blocking for entire system operations feature added, new response for login method added. + 8.1. Login

2.5

2020-03-17

Add information about card bin to responses of methods: Get Card List, Get Friend Card List + 10.3. Get card list + 11.4. Get friend card list

2.4

2020-03-05

New response code from Monitoring service added: ERROR_FUNDING_BANK_IS_BLOCKED, ERROR_PAYMENT_BANK_IS_BLOCKED + 3.1.3 Check status + 3.2.3 Check status 3ds

2.3

2020-01-31

Information about certification process added

2.2

2019-10-11

Regular expression added to models + 13. Models

2.1

2019-09-26

New response code from Monitoring service added + 3.1.3 Check status + 3.2.3 Check status 3ds

2.0

2019-09-16

New response code added + 3.1.3 Check status + 3.2.3 Check status 3ds

1.9

2019-09-06

New response code added + 3.1.3 Check status + 3.2.3 Check status 3ds

1.8

2019-07-17

Regexp for Postal code properties in each occurrences was changed

1.7

2019-07-10

ISO-8583 statuses updated

1.6

2019-04-26

Datacenter migration. + Removed fields from here: 9.1 Add user + -acceptMarketing + -acceptTos + -dailyLimit

1.5

2019-03-21

Added new method to check deposit state for CASH_CARD Merchants + 7. Check deposit state

1.4

2019-01-10

Tutorial and FAQ pages added: + 14. FAQ + Tutorial

1.3

2019-01-02

Added new transaction error status: ERROR_MPI_STATUS_TO_LOW: 3.2.3 Response→ 500 INTERNAL SERVER ERROR

1.2

2018-11-27

Documentation updated. Change description about response field "prefix" in: 9.5. Get countries

1.1

2018-11-22

Documentation updated. Added information about errors related to incompatible country codes of User and User’s card for USA or CAN transaction in: 3.1.2. Response→ 200 OK - Error validation, 3.2.2. Response → 200 OK - Error validation.

1.0

2018-06-25

First release of documentation.

2. Introduction

Document describes technical scope of the "Fenige Transfer HUB REST API" i.e. services, which is financial institution that processes credit or debit card payments.

Quick tutorial that may helps you in works with API you can find here: Tutorial

Implementation of Fenige Transfer HUB REST API

Documentation has been prepared for external partners that are willing to cooperate with Fenige and offer MoneySend card-to-card P2P transactions inside their mobile or web applications. The roles of Fenige and Partner in such project are the following:

Partner:

  • can act as Payment Institution in front of Mastercard/Visa and Financial Regulators in the country

  • operates mobile or web application via which customers can initiate MoneySend/Visa Direct transactions

  • collects customer data during transaction and transfers it to Fenige via Rest API for transaction authorization and clearing

  • decides on consumer fees per transaction that are charged by Fenige during transaction

  • receives agreed fees for MoneySend/Visa Direct transactions from Fenige

Fenige:

  • can act as Payment Institution in front of Mastercard/Visa and Financial Regulators in the country

  • operates transaction processing system that enables authorization and clearing of MoneySend/Visa Direct transactions initiated at partner application

  • process transaction and necessary customer data

  • provides Rest API to partner so that partner is able to initiate transaction

  • is responsible for settlement of transactions with issuers of cards provided by customers

  • transfers agreed fees to Partner one per month

High Level Architecture:

High Level Architecture
Figure 1. High Level Architecture

Transaction process:

  1. Consumer registers at partner mobile or web application

  2. Partner collects consumer and card data that are necessary to process transaction

  3. Fenige MoneySend Hub receives transaction data from Partner system

  4. Fenige transfers transaction data to MasterCard network and process responses

  5. Fenige settles transaction with MasterCard

  6. Fenige transfer agreed transaction fees to Partner

Partner can initiate a few optional methods via Fenige hub that enable processing of MoneySend transaction:

  1. Check limits

  2. Calculate commission

  3. Send money

SM PLAIN PLAIN

There are also optional methods that can be used by partners which store card data at Fenige or Verestro systems:

  1. Log user

  2. Verify 3DS

2.1. Endpoints

Environment Endpoint (base url)

Staging

https://java-staging.fenige.pl:8181/

2.2. HTTP verbs

RESTful notes tries to adhere as closely as possible to standard HTTP and REST conventions in its use of HTTP verbs.

Verb Usage

GET

Used to retrieve a resource

POST

Used to create a new resource

PUT

Used to update specific resource

DELETE

Used to delete a resource

2.3. User authentication

Authentication in HUB API is done by basic authentication and two token mechanism.

  1. API-TOKEN - we can use this authentication method when client is integrated only with HUB application.

  2. X-Request-Token, X-Device-ID - this authentication method is using by mobile devices which are in communication with different server.

User authentication

2.4. Language

If you want to select your language, add Accept-Language header to request JSON and set its value to, for example, pl, en, cs or sk. In case of a successful transaction for the send money method you will receive a email confirmation in the language which you set.

Accept-Language

en

2.5. General methods

All api methods require the delivery of appropriate headers.

List of methods headers used in Fenige REST API:

Key Value Validation Description

Content-Type

application/json

Required

Used to indicate the media type of the resource

Content-Type

application/vnd.sendmoney.v2+json

Optional

Used for send-money with multi-currency purpose

Content-Type

application/vnd.sendmoney3ds.v2+json

Optional

Used for send-money-3ds with multi-currency purpose

Content-Type

application/vnd.determine-currencies.v2+json

Optional

Used for determine currencies with multi-currency purpose

Content-Type

application/vnd.calculate-commission.v2+json

Optional

Used for calculate commission with multi-currency purpose

Authorization

Basic dGVzdDp0ZXN0

Required

Used to resolve merchant context of user. Basic Auth from merchant data (merchant name and password). Consist of keyword Basic and string obtained from Base64 coding method for merchant name and password parameter

API-TOKEN

BMT4wKduNftnN3AUkkKnm4BJEqiMKZlcdLiKRtJH9ac=

Optional

Some of the methods require additional authentication. The API-TOKEN is obtained by calling the logUser method. API-TOKEN is valid for 30 minutes

2.6. HTTP status codes

RESTful notes tries to adhere as closely as possible to standard HTTP and REST conventions in its use of HTTP status codes.

Status code Usage

200 OK

The request completed successfully

202 Accepted

The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place

400 Bad Request

The request was malformed. The response body will include an error providing further information

404 Not Found

The requested resource did not exist

500 Internal Server Error

Message occur when an unexpected condition was encountered

2.7. Mastercard/VISA response code (ISO 8583):

Status code Usage

CODE_00

Approved or completed successfully

CODE_01

Refer to card issuer

CODE_02

Refer to card issuer’s special conditions

CODE_03

Invalid merchant

CODE_04

Pick up card (no fraud)

CODE_05

Do not honor

CODE_06

General error

CODE_07

Pick up card, special condition (fraud account)

CODE_08

Honor with ID

CODE_09

Request in progress

CODE_10

Approved for partial amount

CODE_11

Approved (V.I.P)

CODE_12

Invalid transaction

CODE_13

Invalid amount

CODE_14

Invalid account number (no such number)

CODE_15

No such issuer

CODE_16

Approved, update track 3

CODE_17

Customer cancellation

CODE_18

Customer dispute

CODE_19

Re-enter transaction

CODE_20

Invalid response

CODE_21

No action taken

CODE_22

Suspected malfunction

CODE_23

Unacceptable transaction fee

CODE_24

File update not supported by receiver

CODE_25

Unable to locate record in file

CODE_26

Duplicate file update record, old record replaced

CODE_27

File update field edit error

CODE_28

File update file locked out

CODE_29

File update not successful, contact acquirer

CODE_30

Format error

CODE_31

Bank not supported by switch

CODE_32

Completed partially

CODE_33

Expired card

CODE_34

Suspected fraud

CODE_35

Card acceptor contact acquirer

CODE_36

Restricted card

CODE_37

Card acceptor call acquirer security

CODE_38

Allowable PIN tries exceeded

CODE_39

No credit account

CODE_40

Requested function not supported

CODE_41

Lost card, pick up (fraud account)

CODE_42

No universal account

CODE_43

Stolen card, pick up (fraud account)

CODE_44

No investment account

CODE_51

Not sufficient funds

CODE_52

No checking account

CODE_53

No savings account

CODE_54

Expired card or expiration date is missing

CODE_55

Incorrect PIN or PIN missing

CODE_56

No card record

CODE_57

Transaction not permitted to cardholder

CODE_58

Transaction not permitted to acquirer/terminal

CODE_59

Suspected fraud

CODE_60

Card acceptor contact acquirer

CODE_61

Exceeds withdrawal amount limit

CODE_62

Restricted card (card invalid in this region or country)

CODE_63

Security violation (source is not correct issuer)

CODE_64

Original amount incorrect/Transaction does not fulfill AML requirement

CODE_65

Exceeds withdrawal frequency limit

CODE_66

Card acceptor call acquirer’s security department

CODE_67

Hard capture (requires that card be picked up at ATM)

CODE_68

Response received too late

CODE_70

Contact Card Issuer/PIN data required

CODE_71

PIN Not Changed

CODE_74

Different value than that used for PIN encryption errors

CODE_75

Allowable number of PIN tries exceeded

CODE_76

Invalid/nonexistent “To Account” specified/Unsolicited reversal

CODE_77

Invalid/nonexistent “From Account” specified

CODE_78

Invalid/nonexistent account specified (general)/“Blocked, first used”—Transaction from new cardholder, and card not properly unblocked

CODE_79

Life cycle/Already reversed (by Switch)

CODE_80

System not available/No financial impact

CODE_81

Domestic Debit Transaction Not Allowed (Regional use only)/Cryptographic error found in PIN

CODE_82

Policy (Mastercard use only)/Negative CAM, dCVV, iCVV, or CVV results

CODE_83

Fraud/Security (Mastercard use only)

CODE_84

Invalid Authorization Life Cycle

CODE_85

Not declined/No reason to decline a request for address verification, CVV2 verification, or a credit voucher or merchandise return

CODE_86

PIN Validation not possible

CODE_87

Purchase Amount Only, No Cash Back Allowed

CODE_88

Cryptographic failure

CODE_89

Unacceptable PIN—Transaction Declined—Retry/Ineligible to receive financial position information (GIV)

CODE_90

Cutoff is in process (switch ending a day’s business and starting the next. Transaction can be sent again in a few minutes)

CODE_91

Issuer or switch is inoperative/Issuer or switch inoperative and STIP not applicable or not available for this transaction; Time-out when no stand-in; POS Check Service: Destination unavailable; Credit Voucher and Merchandise Return Authorizations: V.I.P. sent the transaction to the issuer, but the issuer was unavailable.

CODE_92

Financial institution or intermediate network facility cannot be found for routing

CODE_93

Transaction cannot be completed. Violation of law

CODE_94

Duplicate transmission

CODE_95

Reconcile error

CODE_96

System malfunction or certain field error conditions

CODE_A1

Additional customer authentication required

CODE_B1

Surcharge amount not permitted on Visa cards (U.S. acquirers only)

CODE_B2

Surcharge amount not supported by debit network issuer.

CODE_N0

Force STIP

CODE_N3

Cash service not available

CODE_N4

Cashback request exceeds issuer limit or appoved limit

CODE_N5

Ineligible for resubmission

CODE_N7

Decline for CVV2 failure

CODE_N8

Transaction amount exceeds preauthorized approval amount

CODE_P2

Invalid biller information

CODE_P5

Denied PIN unblock—PIN change or unblock request declined by issuer

CODE_P6

Denied PIN change—requested PIN unsafe

CODE_Q1

Card Authentication failed

CODE_R0

Stop payment order

CODE_R1

Revocation of authorization order

CODE_R2

Transaction does not qualify for Visa PIN

CODE_R3

Revocation of all authorizations order

CODE_XA

Forward to issuer

CODE_XD

Forward to issuer

CODE_Z3

Unable to go online

CODE_TBA

Customer ID verification failed

CODE_1A

Additional customer authentication required (Europe Region only)

CODE_6P

Verification Failed (Cardholder Identification does not match issuer records)

2.8. Merchant advice codes

Merchant Advice Codes (MACs) are introduced by Mastercard to clearly communicate to merchants the reason for declining transactions, and the course of action that merchants can take. Occurs only for declined transactions if Mastercard returns this information.

Merchant Advice Code Merchant Advice Code Text

01

New account information available

02

Cannot approve at this time, try again later

03

Do not try again

04

Token not supported

21

Stop recurring payment

24

Retry after 1 hour

25

Retry after 24 hours

26

Retry after 2 days

27

Retry after 4 days

28

Retry after 6 days

29

Retry after 8 days

30

Retry after 10 days

40

Consumer non-reloadable prepaid card

41

Consumer single-use virtual card number

2.9. Response codes

RESTful notes tries to adhere as closely as possible to standard HTTP and REST conventions in its use of HTTP status codes.
Code Messages Http code Http status

S0000

SUCCESS

200

OK

S0001

SUCCESS

204

No Content

S0002

Success transaction

200

OK

S0003

Transaction declined, check response code for reason

200

OK

S0004

PENDING

202

Accepted

S0005

Success reverse transaction

200

OK

S0006

Reverse transaction declined, check response code for reason

200

OK

S0008

Transaction declined.

200

OK

S0010

SUCCESS

200

OK

S0011

Refund declined

200

OK

E0111

Invalid format JSON

422

Unprocessable Entity

E0112

User not exists.

404

Not Found

E0113

User is blocked.

422

Unprocessable Entity

E0114

User is not verified.

422

Unprocessable Entity

E0115

Cannot unblock user. User is already blocked by Fenige.

422

Unprocessable Entity

E0122

Merchant not exists.

404

Not Found

E0132

Terminal not exists.

404

Not Found

E0136

Merchant not exists.

404

Not Found

E0137

Default terminal not exist

422

Unprocessable Entity

E0150

Transaction rejected

422

Unprocessable Entity

E0151

Transaction rejected, currency not supported

422

Unprocessable Entity

E0152

Transaction rejected, issuer card not supported

422

Unprocessable Entity

E0153

Transaction declined, problem with MIP connection

500

Internal Server Error

E0154

Failed to fetch transaction details

500

Internal Server Error

E0155

Transaction not exist

404

Not Found

E0156

Transaction rejected, terminal not supported 3ds

422

Unprocessable Entity

E0157

Transaction rejected, card not supported 3ds

422

Unprocessable Entity

E0158

Transaction rejected, maximum transaction amount limit exceeded

422

Unprocessable Entity

E0159

Transaction rejected, restricted transaction amount has occurred

422

Unprocessable Entity

E01580

Transaction rejected. Card is expired.

422

Unprocessable Entity

E01581

Transaction rejected. Not found Card Authentication (3DS 2.X)

422

Unprocessable Entity

E01582

Transaction rejected. Card Authentication not match to transaction type (3DS 2.X)

422

Unprocessable Entity

E01583

Transaction rejected. Outside 3ds is required for terminal

422

Unprocessable Entity

E01584

Transaction rejected, 3DS 2.X flow invoked for other card number than specified in the request

422

Unprocessable Entity

E01585

Transaction rejected, Outside 3ds values are not valid for Card Authentication.

422

Unprocessable Entity

E01590

Transaction rejected, cof card not found in db

422

Unprocessable Entity

E01591

Transaction rejected, initial cof transaction not approved

422

Unprocessable Entity

E01592

Transaction rejected, recurring card not found in db

422

Unprocessable Entity

E01593

Transaction rejected, initial recurring transaction not cleared

422

Unprocessable Entity

E01594

Transaction rejected, transactionXId parameter had registered for another transaction

422

Unprocessable Entity

E01596

Transaction rejected, terminal blocks transactions with card issued in given card country

422

Unprocessable Entity

E01598

Transaction rejected, ECI value is not available for card provider

422

Unprocessable Entity

E01599

Transaction declined, processing timeout

500

Internal Server Error

E01600

Transaction rejected, 3DS 2.X flow invoked for other card number than specified in the request

422

Unprocessable Entity

E01601

Transaction rejected, terminal is blocked for provider

422

Unprocessable Entity

E01602

Transaction rejected, geographic scope is not permitted for this transaction

422

Unprocessable Entity

E01603

Transaction rejected, Transactions without 3ds above 30 EUR (the blockade applies only to EU countries)

423

Locked

E01604

Transaction rejected, transactions 3DS 1.X not supported for given country

422

Unprocessable Entity

E01605

Transaction rejected, minimum transaction amount limit exceeded

422

Unprocessable Entity

E01606

Transaction rejected, country of residence is not permitted

422

Unprocessable Entity

E01607

Transaction rejected, internal server error during authorization request generation

422

Unprocessable Entity

E01608

Error validation

422

Unprocessable Entity

E01609

Calculated commission for given UUID is expired or does not exists

422

Unprocessable Entity

E01610

Calculated commission has other values than transaction

422

Unprocessable Entity

E01611

Amount is to small

422

Unprocessable Entity

E01612

Mastercard mac tpe excellence rule

422

Unprocessable Entity

E01613

Error sender country is required for merchant crypto

422

Unprocessable Entity

E01614

Receiver country of residence is required for merchant crypto

422

Unprocessable Entity

E01615

Merchant crypto outside eea uk not supported

422

Unprocessable Entity

E01616

Error phone already exists

422

Unprocessable Entity

E01617

Card with phone number already exists

422

Unprocessable Entity

E01618

Error not authorized

422

Unprocessable Entity

E01619

API token not found

422

Unprocessable Entity

E01620

Error 3DS failed

422

Unprocessable Entity

E01621

Required data not complete

422

Unprocessable Entity

E01622

3DS 2.X flow invoked for other merchant

422

Unprocessable Entity

E01623

Sender card is blocked

422

Unprocessable Entity

E01624

Receiver card is blocked

422

Unprocessable Entity

E01625

Sender user is blocked

422

Unprocessable Entity

E01626

Receiver user is blocked

422

Unprocessable Entity

E01627

Sender bin is blocked

422

Unprocessable Entity

E01628

Receiver bin is blocked

422

Unprocessable Entity

E01631

Funding bank is blocked

422

Unprocessable Entity

E01632

Payment bank is blocked

422

Unprocessable Entity

E01633

Possible soft decline alert

422

Unprocessable Entity

E01634

Error user verification

422

Unprocessable Entity

E01635

Error mail verification

422

Unprocessable Entity

E01636

Error merchant or card country same as receiver bank not permitted

422

Unprocessable Entity

E01637

Error sender country is required for account transfers

422

Unprocessable Entity

E01638

Error sender personalId is required for account transfers

422

Unprocessable Entity

E01639

Transaction rejected, terminal blocks transactions with specified country

422

Unprocessable Entity

E01640

Transaction rejected, terminal does not support blik

422

Unprocessable Entity

E01641

Error merchant or card country is not permitted

422

Unprocessable Entity

E0160

Reversal of the payment is processing

422

Unprocessable Entity

E0161

Can’t reversal payment

422

Unprocessable Entity

E0162

Payment is already reversed

422

Unprocessable Entity

E0163

Payment is already refunded

422

Unprocessable Entity

E0164

Reversal rejected. Attempts to refund was made.

422

Unprocessable Entity

E0165

Reversal for transaction exists.

409

Conflict

E0166

Reversal rejected. The time for making the reversal has expired.

422

Unprocessable Entity

E0167

Reversal rejected. Reversal amount exceed transaction amount.

422

Unprocessable Entity

E0170

Clearing of the payment is processing

422

Unprocessable Entity

E0171

Can’t clear payment

422

Unprocessable Entity

E0172

Can’t clear payment, the time is over

422

Unprocessable Entity

E0173

Payment is automatically cleared

422

Unprocessable Entity

E0174

Payment is already cleared

422

Unprocessable Entity

E0175

Can’t clear payment, clearing amount is to low

422

Unprocessable Entity

E0176

Can’t clear payment, clearing amount is to high

422

Unprocessable Entity

E0180

Refund rejected, no MC/VISA response

500

Internal Server Error

E0181

Refund rejected by MC/VISA

500

Internal Server Error

E0182

Refund transaction amount to low

400

Bad Request

E0183

Refund transaction amount to high

400

Bad Request

E0184

Transaction is refunded

422

Unprocessable Entity

E0185

Transaction not cleared, can’t refund

422

Unprocessable Entity

E0186

Refund is already processing

422

Unprocessable Entity

E0187

Transaction is chargeback reported

422

Unprocessable Entity

E0188

Refund rejected. Merchant is not active

500

Internal Server Error

E0189

Refund rejected. Transaction was not approved

422

Unprocessable Entity

E00180

Refund rejected. The time for making the return has expired

422

Unprocessable Entity

E00181

Refund rejected. Refunds for Openbanking transactions should be done on the merchant’s side.

422

Unprocessable Entity

E0190

Failed to get currency rates

500

Internal Server Error

E0200

Transaction rejected, card is blocked

422

Unprocessable Entity

E0201

Transaction rejected, bin is blocked

422

Unprocessable Entity

E0202

Transaction rejected, terminal is blocked

422

Unprocessable Entity

E0203

Transaction rejected, token is blocked

422

Unprocessable Entity

E0204

Transaction rejected, user is on aml list

422

Unprocessable Entity

E0205

Transaction rejected, bank is blocked

422

Unprocessable Entity

E0206

Transaction rejected, too many reject transactions and card is blocked

422

Unprocessable Entity

E0207

Transaction rejected, too many attempts declined and card is blocked

422

Unprocessable Entity

E0208

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days

422

Unprocessable Entity

E0209

Transaction rejected, sender name contains fraudulent phrase.

422

Unprocessable Entity

E0210

Transaction rejected, suspicious sender name.

422

Unprocessable Entity

E0211

Transaction rejected, card country restricted.

422

Unprocessable Entity

E0212

Sender card country restricted

422

Unprocessable Entity

E0213

Receiver card country restricted

422

Unprocessable Entity

E0300

Error mpi V2 - failed internal

500

Internal Server Error

E0301

Three DS Method Data mismatch

422

Unprocessable Entity

E0302

Error on parsing Three DS Method Data

422

Unprocessable Entity

E0303

Card number not Enrolled in 3DS v2

422

Unprocessable Entity

E0304

Invalid card authentication id

422

Unprocessable Entity

E0305

Issuer card is not supported

422

Unprocessable Entity

E0306

Invalid card number

422

Unprocessable Entity

E0307

Card Authentication not found

404

Not Found

E0309

Protocol version is not supported

422

Unprocessable Entity

E0310

Invalid Three DS Method Data

422

Unprocessable Entity

E0311

3DS required

422

Unprocessable Entity

E0400

Failed to get currency for card

500

Internal Server Error

E0401

Issuer card is not supported

422

Unprocessable Entity

E05000

Installment Payment initial not found

500

Internal Server Error

E05001

Installment Payment already confirmed

500

Internal Server Error

E05002

Installment Payment already cancelled

500

Internal Server Error

E05003

Installment Payment already pay in full

500

Internal Server Error

E05004

Installment Payment not confirmed in required time

500

Internal Server Error

E05005

Installment Payment Initial was failed

500

Internal Server Error

E05006

Installment Payment could not find valid installment plan for requested uuid

500

Internal Server Error

E05007

Installment Payment Option not allowed for transaction

500

Internal Server Error

E05008

Installment Payment missing plan uuid

500

Internal Server Error

E05009

Installment Payment missing request number of installments

500

Internal Server Error

E05010

Installment Payment requested number of installments is outside of allowed range

500

Internal Server Error

E05011

Installment Payment operation not allowed, installment type allows ISSUER_FINANCED installments

500

Internal Server Error

E05012

Installment Payment reverse not allowed

500

Internal Server Error

E05013

Installment Payment refund not allowed

500

Internal Server Error

E05014

Installment Payment outside 3ds request is required for terminal

500

Internal Server Error

E05015

Installment Payment unsupported card provider VISA

500

Internal Server Error

E06003

Datacenter card not found

404

Not Found

E06004

Delete of ecommerce card failed, card not found

422

Unprocessable Entity

E06005

Update of ecommerce card failed, card not found

422

Unprocessable Entity

E06007

Exception occurred while trying to add ecommerce card

422

Unprocessable Entity

E7001

Request id is exploited

400

Bad Request

E7002

Service not available

503

Service Unavailable

E8000

Bad Request

400

Bad Request

E8001

Forbidden

403

Forbidden

E8012

Not found

404

Not Found

E8002

Unauthorized

401

Unauthorized

E8003

Scale of amount is different than the scale of currency

422

Unprocessable Entity

E8004

Some operation for this requestUuid is processing

422

Unprocessable Entity

E8009

Merchant RSA keys not found

404

Not Found

E8010

Merchant RSA key expired

422

Unprocessable Entity

E8011

Internal error during card decrypting

500

Internal Server Error

E9000

Domain error

500

Internal Server Error

E9001

Error acquirer connection

503

Service Unavailable

E9002

Error mpi connection

503

Service Unavailable

E9003

Error monitoring connection

503

Service Unavailable

E9010

Error data center connection

503

Service Unavailable

E9800

Error blik connection.

503

Service Unavailable

E9011

Error limit connection

503

Service Unavailable

E9012

Error mms connection

503

Service Unavailable

E10000

Transaction rejected, terminal daily card transaction limit exceeded

422

Unprocessable Entity

E10001

Transaction rejected, terminal daily transaction limit exceeded

422

Unprocessable Entity

E10002

Transaction rejected, terminal monthly transaction limit exceeded

422

Unprocessable Entity

E10003

Transaction rejected, limit exceeded

422

Unprocessable Entity

E10004

Transaction rejected, contractor daily transaction limit exceeded for Mastercard provider

422

Unprocessable Entity

E10005

Transaction rejected, contractor monthly transaction limit exceeded for Mastercard provider

422

Unprocessable Entity

E10006

Transaction rejected, contractor daily transaction limit exceeded for Visa provider

422

Unprocessable Entity

E10007

Transaction rejected, contractor monthly transaction limit exceeded for Visa provider

422

Unprocessable Entity

E10008

Transaction rejected, contractor daily transaction limit exceeded

422

Unprocessable Entity

E10009

Transaction rejected, contractor monthly transaction limit exceeded

422

Unprocessable Entity

E10010

Error single transaction limit

422

Unprocessable Entity

E10011

Error daily transaction limit

422

Unprocessable Entity

E10012

Error weekly transaction limit

422

Unprocessable Entity

E10013

Error daily count transaction limit

422

Unprocessable Entity

E10014

Error monthly transaction limit

422

Unprocessable Entity

E10015

Error monthly count transaction limit

422

Unprocessable Entity

E10016

Error daily cumulative limit

422

Unprocessable Entity

E10017

Error monthly cumulative limit

422

Unprocessable Entity

E10018

Error merchant mastercard daily cumulative limit

422

Unprocessable Entity

E10019

Error merchant mastercard monthly cumulative limit

422

Unprocessable Entity

E10020

Error merchant visa daily cumulative limit

422

Unprocessable Entity

E10021

Error merchant visa monthly cumulative limit

422

Unprocessable Entity

E10022

Error merchant daily cumulative limit

422

Unprocessable Entity

E10023

Error merchant monthly cumulative limit

422

Unprocessable Entity

E11000

Time for processing exceeded.

500

Internal Server Error

E12000

Error occurred during decrypting the message

422

Unprocessable Entity

E13000

Transaction rejected, risk score exceeded

422

Unprocessable Entity

E13001

Transaction rejected, risk status REJECTED

422

Unprocessable Entity

E14000

Waiting for receiver timeout

422

Unprocessable Entity

E14001

Error delayed payment not found

422

Unprocessable Entity

E14002

Error delayed payment attempts exceeded

422

Unprocessable Entity

E14003

Error delayed payment receiver not present

422

Unprocessable Entity

E14004

Error delayed payment receiver not specified

422

Unprocessable Entity

E14005

Error delayed payment unexpected exception occurred

422

Unprocessable Entity

E14006

Error delayed payment trx not registered for delayed processing

422

Unprocessable Entity

E14007

Error delayed payment datacenter receiver not found

422

Unprocessable Entity

E14008

Error delayed payment datacenter card not found

422

Unprocessable Entity

E14009

Error delayed payment datacenter adding receiver failed

422

Unprocessable Entity

E14010

Error delayed payment datacenter adding card failed

422

Unprocessable Entity

E15000

Error card unprovisioned

422

Unprocessable Entity

E15001

Error card not eligible

422

Unprocessable Entity

E15002

Error card not allowed

422

Unprocessable Entity

E15003

Error card declined

422

Unprocessable Entity

E15004

Error card service unavailable

500

Internal Server Error

E15005

Error card system error

500

Internal Server Error

E16000

Error cannot process account transfer to specified country code of bank

422

Unprocessable Entity

E16001

Error cannot process account transfer because of internal VISA API error

500

Internal Server Error

E16002

Transaction rejected, account is blocked

422

Unprocessable Entity

3. Send money

See a diagrams bellow and notice that CARD-CARD and CASH-CARD flow are not the same.

Mastercard and Visa requires for intra-European Economic Area (EEA), plus United Kingdom, for which EMV 3DS must be used subsequent to a valid authorization soft decline DE39=65 (Mastercard)/1A(Visa).To perform a transaction for which the card has previously received CODE_65-Mastercard, CODE_1A-VISA, the transaction must be processed with full EMV 3DS (3DS 2.x) and the authentication status must be 'Y'.

Correct flow:

  • 3DS 2.x → Challenge → Authentication status Y → Transaction (Recommended)

  • 3DS 2.x(Authentication status A) → Transaction → CODE_65/CODE_1A → 3DS 2.x → Challenge → Authentication status Y → Transaction (Recommended)

  • non3DS → Transaction → CODE_65/CODE_1A → 3DS 2.x → Challenge → Authentication status Y → Transaction (Available only to selected merchants)

soft decline Code 65 EMV 3DS
CARD - CARD

Is apply for: PLAIN-PLAIN, DATACORE-PLAIN, DATACORE-DATACORE, DATACORE-PHONE

SM PLAIN PLAIN
CASH - CARD

Is apply for: CASH-PLAIN, CASH-PHONE

SM CASH CARD
BLIK - CARD

Is apply for: BLIK-PLAIN

SM BLIK CARD
CASH - ACCOUNT

Is apply for: CASH-ACCOUNT

SM CASH ACCOUNT
CARD - ACCOUNT

Is apply for: PLAIN-ACCOUNT

SM CARD ACCOUNT

3.1. Card to Card

POST /api/v2/client/send-money Content-Type: application/vnd.sendmoney.v2+json, Authorization: Basic Auth, API-TOKEN*
Innovative technology that allows to send money between cards instantly anywhere in the world. No SWIFT or bank account number needed!
Money transfer from card to account number is possible from Q1 2024
This method is used to MoneySend transaction (funding and payment). To enable users to make transfers in any currency, Fenige introduces the send-money method for
multicurrency.
1 - User by selecting type = SENDER defines amount of funding in given currency. This amount is collected from sender card in selected currency.
2 - User by selecting type = RECEIVER defines amount of payment in given currency. This amount is transferred to receiver card in selected currency.
In case there's need revaluation from one currency to another, system uses lowerRate for situation 1 and higherRate for situation 2.
For more details about specific rates please refer to Currency Rate method.
*API-TOKEN is required for methods: DATACORE-PLAIN, PLAIN-DATACORE, DATACORE-DATACORE, DATACORE-PHONE
The API-TOKEN is refreshed each time it is used in the header. The API-TOKEN is refreshed for 30 minutes.
Please notice that you can choose language of email confirmation of this transaction. It is able by attach proper header to request.
SM MULTI CURRENCY
The success of the multicurrency send-money transaction depends primarily on the correctness of the merchant's currency configuration which is done by the admin. To make transactions in a currency other than the currency of the card, contact the admin.
In order to provide users with the ability to safely retry transaction (for example to request for an undelivered response), the v2 of API supports idempotent send money multi-currency operation.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

When performing authorization, remember that there are currencies with different number of decimal places. For example: VND has no pennies and KWD has three decimal places. Please take this into account in the Amout field. For more information on other currencies, see ISO 4217.

Worth to note are the new CARD_ACCOUNT and CASH_ACCOUNT transaction models. Using this transaction model, we can quickly make a transfer from a card to an account number or from a Fenige cash deposit to an account number. Transactions in this model are very simple and differ slightly from normal card-to-card transactions. Only the receiver object is changed. An important piece of information to ensure high transaction compliance is the ability to execute the /client/send-money/validate method, which will make sure that your request body is correct and can be processed correctly in a real transaction with the /api/v2/client/send-money method. Your request body will be validate in Visa/Mastercard side so we can be sure that information you gathered is correct. Look at the PLAIN-ACCOUNT tab

3.1.1. Request

Request fields

Table 1. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies)

cvc2

String

Required

@Length(min = 3, max = 3)

Sender card cvc2/cvv2

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender PLAIN Sender CASH Sender DATACORE Sender BLIK

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver DATACORE Receiver PHONE Receiver ACCOUNT

Example HTTP Request
PLAIN-PLAIN
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 877
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "f316fbd4-9a35-4272-962b-a097ec1499b3",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
PLAIN-DATACORE
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 903
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "6860dada-2a85-4357-a479-a107f9717057",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DATACORE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-PLAIN
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 798
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "de18094b-bb75-4ed7-bc30-46a0f83c9178",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-DATACORE
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 824
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "fd0b3b26-2e5d-47e0-97ed-b54a50e5e204",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DATACORE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-PHONE
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 794
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "4c05f5a4-22dc-4a52-8e9d-38538136847f",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PHONE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "phoneNumber" : "48123777619",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
SM DATACORE PHONE
PLAIN-ACCOUNT
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1180
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "14c8b152-532d-4c1c-92a4-ae259a765fba",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "country" : "PL",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}
PLAIN-ACCOUNT (Validation)
POST /client/send-money/validate HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 957
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "32a99272-6e82-47ea-b034-c571dcc5ac45",
  "transactionId" : "TRX220132AM",
  "cvc2": "123",
  "sender" : {
    "type" : "PLAIN",
    "firstName": "Rob",
    "lastName": "Meksuła",
    "street": "Wring",
    "houseNumber": "17A",
    "city": "Lublin",
    "postalCode": "20-400",
    "flatNumber": "2",
    "email": "rob.wring@fenige.pl",
    "birthDate": "1993-01-16",
    "cardNumber": "5117964247989169",
    "expirationDate": "03/26",
    "personalId": "AGC688910",
    "currency": "PLN",
    "country": "PL"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2023-12-13",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}

3.1.2. Response

Response status
Status Description

200 OK - Error validation

Returned list of field name which has validation errors.

202 Accepted

- Returned when the transaction with the provided requestId has been registered in the system, but has not yet been completed. The user can retry in a few seconds to get the transaction result. Response body: Empty
or
- Returned order-id when transaction will be processed.

400 Bad Request

Returned e.g. when a different transaction with the provided requestId has already been registered in the system.

401 Unauthorized

Returned when API-TOKEN was broken.

Example HTTP Response
202 Accepted
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 56

{
  "orderId" : "846647ee-8268-4e5d-8a4a-64267834ed1b"
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier

400 Bad request
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 104

{
  "error" : {
    "message" : "Another transaction with the same id has already been processed."
  }
}
200 OK - Error validation
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
	"status": "ERROR_VALIDATION",
	"error": {
		"message": "Some information is missing or incorrect.",
		"errors": [{
				"field": "requestId",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "cvc2",
				"message": [
					"may not be null",
					"length must be 3"
				]
			},
			{
				"field": "type",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "amount",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
				"field": "sender.expirationDate",
				"message": [
					"invalid card expiration date",
					"may not be null",
					"may not be empty"
				]
			},
			{
				"field": "sender.city",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 25"
				]
			},
			{
				"field": "sender.street",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 50"
				]
			},
            {
				"field": "sender.postalCode",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10"
				]
			},
            {
                "field": "sender.flatNumber",
                "message": [
                    "must be null",
                    "length must be between 0 and 5"
                ]
            },
			{
				"field": "sender.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.houseNumber",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10",
                    "must match the expression: ^[1-9][0-9]{0,4}(?:[A-z]?[0-9]{0,4})?((?:[-/ ][1-9]?[A-z]?[0-9]{0,4})*[A-z]?)?$"
				]
			},
			{
				"field": "sender.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
            {
				"field": "sender.email",
				"message": [
					"may not be empty",
					"may not be null",
					"not a well-formed email address",
					"lenght must be beetween 1 and 128"
				]
			},
			{
				"field": "receiver",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.currency",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
                "field": "sender",
                "message": [
                     "province is mandatory only if country code is US or CA"
                ]
            },
            {
                "field": "sender.province",
                "message": [
                      "is not correct province code for country code US",
                      "may not be null"
                ]
            },
            {
                "field": "sender.province",
                 "message": [
                       "may not be null",
                       "is not correct province code for country code CA"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                        "must match ^[A-Z]{2}$",
                        "is not correct province code for country code US"
                 ]
            },
            {
                 "field": "sender.currency",
                 "message": [
                       "Currency is not supported"
                ]
            },
            {
                 "field": "receiver.currency",
                 "message": [
                       "Currency is not supported"
                ]
            }
		]
	}
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_API_TOKEN_NOT_FOUND",
    "error": {
        "message": "API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver."
    }
}
401 UNAUTHORIZED
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "Username or password is not correct",
      "path": "/api/v2/client/send-money"
}
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "ERROR_USER_NOTFOUND",
      "path": "/api/v2/client/send-money"
}
Table 2. Response fields
Path Description

timestamp

Time when request was executed

status

Http response code

error

Http status name

message

Message for response code

path

Path to a specific resource

403 FORBIDDEN
HTTP Response - Error
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
    "timestamp": 1610464313387,
    "status": 403,
    "error": "Forbidden",
    "message": "No message available",
    "path": "/client/send-money-3ds"
}

3.1.3. Check status

GET /client/send-money/{orderId}, Authentication: Basic Auth
The method allows obtaining a status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 3. /client/send-money/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

500 INTERNAL SERVER ERROR

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1123

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  }
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1

PAYMENT_TRANSACTION_DECLINED:CODE_05

After receiving these statuses, the transaction was rejected

Error statuses

Name Description

FUNDING_TRANSACTION_DECLINED:CODE_XX, PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

ISSUER_NOT_SUPPORTED

This card is not supported

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

ERROR_FUNDING_BANK_IS_BLOCKED

Funding bank is blocked in Fenige

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

FUNDING_TRANSACTION_DECLINED:ACQ_ERROR [only for CARD-CARD]

Funding transaction was declined and payment not send

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

AML_ERROR

User was found on the stop list

NETWORK_ERROR

Acceptance network is unavailable

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

CURRENCY_NOT_SUPPORTED

Currency is not supported

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

ERROR_WEEKLY_TRANSACTION_LIMIT

Weekly transaction limit for amount per card exceeded

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_SENDER_CARD_IS_BLOCKED [only for CARD-CARD]

Sender’s card is blocked

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

ERROR_SENDER_USER_IS_BLOCKED [only for CARD-CARD]

User acting as sender is blocked

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

ERROR_SENDER_BIN_IS_BLOCKED [only for CARD-CARD]

BIN of sender’s card is blocked

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

ERROR_MONITORING

Some unrecognized error occurred

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

FUNDING_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

FUNDING_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION [only for CARD-CARD]

Funding process failed and it is need to manual verification of transaction

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

FUNDING_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip_proxy response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

REJECTED [only for CASH-CARD]

Amount exceeds current merchant deposit limit

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

ERROR_CARD_NOT_FOUND

Card was not found

ERROR_DATACORE_CONNECTION

Problem with DC

ERROR_SOMETHING_WRONG

ERROR_SOMETHING_WRONG returned when the check status method is executed means that the details for the indicated transaction could not be retrieved correctly due to an unexpected error. This does not mean that the transaction was rejected by our system. In case of receiving ERROR_SOMETHING_WRONG status, please do not hesitate to notify our support team in order to determine the correctness of the transaction execution and quickly correct the method error.

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE_FOR_PLAIN

This error may occur if card’s country is other than user’s country for USA or CAN transaction for PLAIN model

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE

This error may occur if card’s country is other than user’s country for USA or CAN transaction

ERROR_WHILE_GETTING_COUNTRY_CODE

This error may occur when system could not get card country code. Most often, the error is caused by a missing card in the parameters received from the card provider.

ERROR_WHILE_VALIDATING_PROVINCE_NOT_CORRECT_PROVINCE_CODE

Province code is not valid for USA or CAN transactions. Please update user profile

ERROR_VALIDATION

Some validation error occurred

ERROR_VALIDATION Sender type violates merchant model

This error may occur when merchant tries to make transaction in other model than assigned primarily. For example, if merchant’s model is set as CARD-CARD and then merchant will try to make transaction in CASH-CARD model, will receive error as bellow.

ERROR_VALIDATION_EXPIRY_DATE

Card expired

AMOUNT_IS_TOO_SMALL

The amount sent is too small. Enter a larger amount.

AMOUNT_IS_TOO_HIGH

The amount sent is too high. Enter a lower amount.

ERROR_MERCHANT_FUNDING_CARD_COUNTRY_RESTRICTED

Restricted funding card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_PAYMENT_CARD_COUNTRY_RESTRICTED

Restricted payment card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER

Merchant not support the given card provider, please contact support to check merchant configuration

MERCHANT_CRYPTO_OUTSIDE_EEA_UK_NOT_SUPPORTED

Merchant crypto is not supported outside EEA+UK

ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the receiver card country.

ERROR_FUNDING_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the sender card country.

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

ERROR_TRANSACTION_PROCESSING_TIME_TOO_LONG

Processing time of transaction was too long, transaction is declined.

MASTERCARD_MAC_TPE_EXCELLENCE_RULE

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days.

INCORRECT_NAME_DATA

Transaction rejected, sender or receiver name contains fraudulent phrase.

ERROR_NAME_VERIFICATION

Transaction rejected, suspicious sender or receiver name.

ERROR_TRANSACTION_REJECTED_COUNTRY_OF_RESIDENCE_NOT_PERMITTED

Transaction rejected, card country is not supported for merchants crypto.

ERROR_SENDER_COUNTRY_IS_REQUIRED

Transaction card-account rejected, country code in sender object is required for this transactional model

ERROR_SENDER_PERSONAL_ID_IS_REQUIRED

Transaction card-account or cash account rejected, personalId field in sender object is required for this transactional model

ERROR_MERCHANT_OR_CARD_COUNTRY_SAME_AS_RECEIVER_BANK_NOT_PERMITTED

Transaction rejected, country of merchant cannot be the same as receiver’s bank code

3.1.4. Check detailed status

GET /client/send-money/details/{orderId}, Authentication: Basic Auth
    The method allows obtaining a detailed status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money
multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 4. /client/send-money/details/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/details/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

404 NOT FOUND

Returned when a transaction related to the given orderId doesn’t exist.

422 UNPROCESSABLE ENTITY

Returned when user provides wrong order-id or transaction was failed or was Declined.

500 INTERNAL SERVER ERROR

Returned when an internal error occur.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1159

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "APPROVED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

404 NOT FOUND
HTTP/1.1 404 Not Found
Content-Type: application/json
Content-Length: 51

{
  "errorStatus" : "ERROR_TRANSACTION_NOT_FOUND"
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

422 UNPROCESSABLE ENTITY
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1287

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "DECLINED",
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:25.197",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

Additional data of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

422 UNPROCESSABLE ENTITY CASH-CARD
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1358

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH"
  },
  "transactionStatus" : "DECLINED",
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68,
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:24.637",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

The code of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for declined transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 69

{
  "errorStatus" : "ERROR_SOMETHING_WRONG - Something went wrong."
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

3.1.5. Transaction history

GET /client/{clientId}/transactions?page=0&size=100 Content Type: application/json, Authorization: Basic Auth
Method return page with list of user transactions. Transactions are filtered by clientId provided in GET parameter.
User can send additional optional parameters (page, size) to obtain given page with defined size.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
GET /client/0/transactions?fromDate=2018-03-06&toDate=2018-03-08&page=0&size=100 HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned list of transactions history.

404 NOT FOUND

Returning the list failed.

Example Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1118

{
  "content" : [ {
    "correlationId" : "75044f09-20cf-4508-93e2-2820e5a932f8",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverFirstName" : "Patrick",
    "receiverLastName" : "Evans",
    "receiverHiddenCardNumber" : "511123******1234",
    "receiverProvider" : "MASTERCARD",
    "receiverBankName" : "Bank Polska Kasa Opieki Spółka Akcyjna",
    "receiverEmail" : "receiver@fenige.pl",
    "receiverPhone" : "600300200",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "OUTGOING",
    "3DS" : false
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system

content.[].createdDate

String

Date of transaction processing

content.[].amount

Number

Transaction amount in pennies

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency

content.[].currency

String

Transaction currency

content.[].cardId

Number

Datacore card id used in transaction (sender card)

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].receiverFirstName

String

Transaction receiver first name

content.[].receiverLastName

String

Transaction receiver last name

content.[].receiverHiddenCardNumber

String

Transaction receiver hidden card number

content.[].receiverProvider

String

VISA or MASTERCARD or MAESTRO

content.[].receiverBankName

String

Transaction receiver card bank name.

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card numbe.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverPhone

String

Transaction receiver phone number

content.[].receiverEmail

String

Transaction receiver email

content.[].status

String

Status of the transaction (approved, reversed)

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false)

totalPages

Number

Total number of all pages

totalElements

Number

Total number of all transactions

numberOfElements

Number

Number of transactions on page

first

Boolean

Describes whether the page is first (true ot false)

sort

Object

Details of sort

size

Number

Max number of transactions on page

number

Number

Page number

pageable

String

Page number

404 NOT FOUND
HTTP/1.1 404 Not Found

3.1.6. Transaction details

GET /client/transactions/{orderId} Content Type: application/json, Authorization: Basic Auth
Method return transaction details for single transaction given in method parameter orderId

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
GET /client/transactions/fae3ee90-6f88-4aa6-aff5-7d9f6a5645d3 HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned details of transaction.

Example Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 297

{
  "fundingAmount" : "2.00 PLN",
  "chargedAmount" : "2.04 PLN",
  "commission" : "0.04 PLN",
  "paymentAmount" : "0.54 USD",
  "exchange" : "1.00 PLN = 0.27 USD",
  "transactionTime" : "2018-07-26T17:01:56.364Z",
  "cardIssuer" : "MASTERCARD",
  "amountInUsDollar" : 1,
  "status" : "approved"
}

Response fields

Path Type Description

fundingAmount

String

Funding amount in transaction currency

chargedAmount

String

Charged amount in transaction currency

commission

String

Transaction commission with currency

paymentAmount

String

Payment amount in receiver currency

exchange

String

Revaluation amount from sender to receiver currency

transactionTime

String

Date of the transaction

cardIssuer

String

Card issuer MASTERCARD/VISA

amountInUsDollar

Number

Transaction amount in USD currency in pennies

status

String

Status of transaction approved/reject/decline

3.2. Card to Card 3D Secure

POST /api/v2/client/send-money-3ds Content-Type: application/vnd.sendmoney3ds.v2+json, Authorization: Basic Auth, API-TOKEN*
Innovative technology that allows to send money between cards instantly anywhere in the world. No SWIFT or bank account number needed!
Money transfer from card to account number is possible from Q1 2024
This method is used to MoneySend transaction (funding and payment). To enable users to make transfers in any currency, Fenige introduces the send-money method for
multicurrency.  The method allows executing transactions with additional protection i.e. verification by the 3DS (3D-Secure) in 2.X standard.
1 - User by selecting type = SENDER defines amount of funding in given currency. This amount is collected from sender card in selected currency.
2 - User by selecting type = RECEIVER defines amount of payment in given currency. This amount is transferred to receiver card in selected currency.
In case there's need revaluation from one currency to another, system uses lowerRate for situation 1 and higherRate for situation 2.
For more details about specific rates please refer to Currency Rate method.
*API-TOKEN is required for methods: DATACORE-PLAIN, PLAIN-DATACORE, DATACORE-DATACORE, DATACORE-CASH, DATACORE-PHONE
The API-TOKEN is refreshed each time it is used in the header. The API-TOKEN is refreshed for 30 minutes.
3DS 2.X transaction requires additional parameters, but the flow of transaction is the same as transaction without 3DS.
Please notice that you can choose language of email confirmation of this transaction. It is able by attach proper header to request.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

When performing authorization, remember that there are currencies with different number of decimal places. For example: VND has no pennies and KWD has three decimal places. Please take this into account in the Amout field. For more information on other currencies, see ISO 4217.

Worth to note are the new CARD_ACCOUNT and CASH_ACCOUNT transaction models. Using this transaction model, we can quickly make a transfer from a card to an account number or from a Fenige cash deposit to an account number. Transactions in this model are very simple and differ slightly from normal card-to-card transactions. Only the receiver object is changed. An important piece of information to ensure high transaction compliance is the ability to execute the /client/send-money/validate method, which will make sure that your request body is correct and can be processed correctly in a real transaction with the /api/v2/client/send-money method. Your request body will be validate in Visa/Mastercard side so we can be sure that information you gathered is correct. Look at the PLAIN-ACCOUNT tab

Send money with outside 3DS flow
sendmoney trx outside3ds flow
Send money with outside 3DS and DataCenter flow
sendmoney trx outside3ds datacenter flow

3.2.1. Request

Request fields

Table 5. Multicurrency-3DS
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

cvc2

String

Required

@Length(min = 3, max = 4)

Sender Card cvc2/cvv2.

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

sender

Object

Required

@NotNull

Sender PLAIN Sender DATACORE

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver DATACORE Receiver PHONE

outside3ds.cavv

String

Required

@NotNull

Server transaction Id generated by DS. Required for 3DS 2.X version

outside3ds.eci

String

Required

@NotNull

Electronic Commerce Indicator: 5 (Visa) or 2 (SecureCode) - The cardholder was successfully authenticated. 6 (Visa) or 1 (SecureCode) - Authentication was attempted, but the cardholder was not enrolled. Chargeback protection applies.

outside3ds.authenticationStatus

String

Required

@NotNull

Authentication status. If AuthenticationStatus is "Y" or "A" then outside 3ds flow will be execute.

outside3ds.transactionXId

String

Required

@NotNull

Cardholder Authentication Verification Value. Cardholder Authentication Verification Value. The transactionXId is the field that defines the 3DS version. The presence of this field in the HTTP request specifies that the transaction will be processed with 3DS 2.x.TransactionXId can be obtained by executing the /authentication method.

Example HTTP Request
PLAIN-PLAIN
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1025
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "679d310c-4bf5-4148-9422-19c0edf83cc1"
  },
  "requestId" : "d3dc6787-1b8a-485a-84de-56779eacca27",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
PLAIN-DATACORE
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 1051
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "43107396-2f0e-43fa-981d-8bc1d15e8987"
  },
  "requestId" : "98d6d7b6-4cd7-4da5-b01b-c16f2c7c9f49",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DATACORE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-PLAIN
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 946
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "934556bb-ab63-4cf7-b3b4-712a98d065df"
  },
  "requestId" : "780df668-cdf9-4073-9f1c-c8d130f5cd0c",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-DATACORE
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 972
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "3b21bf60-28a3-40d6-8195-0455eaa336b0"
  },
  "requestId" : "18c47465-e955-47f6-9c3a-2ef5bfbbc6cf",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DATACORE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
DATACORE-PHONE
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 942
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "cfa47f9d-c112-49f8-a4f5-56602e0ba683"
  },
  "requestId" : "6e808156-656f-44c8-be5c-6671c3e51fcf",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "PHONE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "phoneNumber" : "48123777619",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}
SM 3DS DATACORE PHONE
PLAIN-CASH
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1092
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "7bd771d6-fc27-4200-81f4-f1db6b58b750"
  },
  "requestId" : "3bf93a12-ac24-471c-9780-d5f27a81cd7c",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "CASH",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "street" : "Lubelska",
    "houseNumber" : "17A",
    "city" : "Lubartów",
    "postalCode" : "21-100",
    "flatNumber" : "2",
    "email" : "receiverEmail@fenige.pl",
    "country" : "PL"
  }
}
DATACORE-CASH
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 1013
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "85821bc4-cf5b-4ab1-b124-a6fe57a3f729"
  },
  "requestId" : "9ef7fa65-68a7-4823-9c9e-058f41699085",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "CASH",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "street" : "Lubelska",
    "houseNumber" : "17A",
    "city" : "Lubartów",
    "postalCode" : "21-100",
    "flatNumber" : "2",
    "email" : "receiverEmail@fenige.pl",
    "country" : "PL"
  }
}
PLAIN-ACCOUNT
POST /api/v2/client/send-money-3ds HTTP/1.1
Content-Type: application/vnd.sendmoney3ds.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1328
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "authenticationStatus" : "Y",
    "eci" : "01",
    "transactionXId" : "32a4f18d-cbd6-4cdb-95ec-a660d1f7e107"
  },
  "requestId" : "a06f03ca-3605-4bc4-8d9d-d47a647bdfef",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "country" : "PL",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}
PLAIN-ACCOUNT (Validation)
POST /client/send-money/validate HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 957
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "32a99272-6e82-47ea-b034-c571dcc5ac45",
  "transactionId" : "TRX220132AM",
  "cvc2": "123",
  "sender" : {
    "type" : "PLAIN",
    "firstName": "Rob",
    "lastName": "Meksuła",
    "street": "Wring",
    "houseNumber": "17A",
    "city": "Lublin",
    "postalCode": "20-400",
    "flatNumber": "2",
    "email": "rob.wring@fenige.pl",
    "birthDate": "1993-01-16",
    "cardNumber": "5117964247989169",
    "expirationDate": "03/26",
    "personalId": "AGC688910",
    "currency": "PLN",
    "country": "PL"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2023-12-13",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}

3.2.2. Response

Response status
Status Description

200 OK

Returned if the transaction completes successfully.

200 OK - Error validation

Returned list of field name which has validation errors.

202 Accepted

Returned when the transaction with the provided requestId has been registered in the system, but has not yet been completed. The user can retry in a few seconds to get the transaction result.

400 Bad Request

Returned e.g. when a different transaction with the provided requestId has already been registered in the system.

401 Unauthorized

Returned when API-TOKEN was broken.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 54

{
	"orderId": "234abf25-c35f-a263-a402-cbaf874f137a"
}

Response fields

Path Type Description

orderId

String

OrderId

200 OK - Error validation
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
	"status": "ERROR_VALIDATION",
	"error": {
		"message": "Some information is missing or incorrect.",
		"errors": [{
				"field": "requestId",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "cvc2",
				"message": [
					"may not be null",
					"length must be 3"
				]
			},
			{
				"field": "amount",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "type",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender.houseNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 10"
				]
			},
            {
				"field": "sender.street",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 50"
				]
			},
			{
				"field": "sender.firstName",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.postalCode",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10"
				]
			},
            {
				"field": "sender.city",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 25"
				]
			},
            {
                "field": "sender.flatNumber",
                "message": [
                    "must be null",
                    "length must be between 0 and 5"
                ]
            },
			{
				"field": "sender.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
				"field": "sender.email",
				"message": [
					"may not be empty",
					"may not be null",
					"not a well-formed email address",
					"lenght must be beetween 1 and 128"
				]
			},
			{
				"field": "sender.expirationDate",
				"message": [
					"invalid card expiration date",
					"may not be null",
					"may not be empty"
				]
			},
			{
				"field": "receiver",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.firstName",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.currency",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
				    "card number length must be 16"
				]
			},
			{
                "field": "sender",
                "message": [
                     "province is mandatory only if country code is US or CA"
                ]
            },
            {
                 "field": "sender.province",
                 "message": [
                      "is not correct province code for country code US",
                      "may not be null"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                       "may not be null",
                       "is not correct province code for country code CA"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                        "must match ^[A-Z]{2}$",
                        "is not correct province code for country code US"
                 ]
            },
            {
                 "field": "sender.currency",
                 "message": [
                       "Currency is not supported"
                ]
            },
            {
                 "field": "receiver.currency",
                 "message": [
                       "Currency is not supported"
                ]
            }
        ]
    }
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_API_TOKEN_NOT_FOUND",
    "error": {
        "message": "API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver."
    }
}
202 Accepted
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 56

{
  "orderId" : "d38fb311-e50c-4777-9cd4-f94ddd8e13a1"
}

Response fields

Path Type Description

orderId

String

Transaction order-id

400 Bad request
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 104

{
  "error" : {
    "message" : "Another transaction with the same id has already been processed."
  }
}
401 UNAUTHORIZED
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "Username or password is not correct",
      "path": "/api/v2/client/send-money-3ds"
}
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "ERROR_USER_NOTFOUND",
      "path": "/api/v2/client/send-money-3ds"
}
Table 6. Response fields
Path Description

timestamp

Time when request was executed

status

Http response code

error

Http status name

message

Message for response code

path

Path to a specific resource

403 FORBIDDEN
HTTP Response - Error
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
    "timestamp": 1610464313387,
    "status": 403,
    "error": "Forbidden",
    "message": "No message available",
    "path": "/client/send-money-3ds"
}

3.2.3. Check status

GET /client/send-money-3ds/{orderId}, Authentication: Basic Auth
The method allows obtaining a status of 3ds transaction specified by order-id. Parameter order-id was returned in the previous step (Send money multicurrency 3DS).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 7. /client/send-money-3ds/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money-3ds/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

500 INTERNAL SERVER ERROR

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 986

{
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  }
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

createdDate

String

Date of transaction.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

200 OK (For PLAIN-CASH, DATACORE-CASH models)
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 946

{
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "CASH",
    "hiddenCardNumber" : "****************"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  }
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

createdDate

String

Date of transaction.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1

PAYMENT_TRANSACTION_DECLINED:CODE_05

After receiving these statuses, the transaction was rejected

Error statuses

Name Description

FUNDING_TRANSACTION_DECLINED:CODE_XX, PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

ISSUER_NOT_SUPPORTED

This card is not supported

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

ERROR_FUNDING_BANK_IS_BLOCKED

Funding bank is blocked in Fenige

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

FUNDING_TRANSACTION_DECLINED:ACQ_ERROR [only for CARD-CARD]

Funding transaction was declined and payment not send

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

AML_ERROR

User was found on the stop list

NETWORK_ERROR

Acceptance network is unavailable

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

CURRENCY_NOT_SUPPORTED

Currency is not supported

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

ERROR_WEEKLY_TRANSACTION_LIMIT

Weekly transaction limit for amount per card exceeded

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_SENDER_CARD_IS_BLOCKED [only for CARD-CARD]

Sender’s card is blocked

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

ERROR_SENDER_USER_IS_BLOCKED [only for CARD-CARD]

User acting as sender is blocked

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

ERROR_SENDER_BIN_IS_BLOCKED [only for CARD-CARD]

BIN of sender’s card is blocked

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

ERROR_MONITORING

Some unrecognized error occurred

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

FUNDING_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

FUNDING_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION [only for CARD-CARD]

Funding process failed and it is need to manual verification of transaction

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

FUNDING_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip_proxy response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

ERROR_FINALIZE_3DS_NOT_AUTHENTICATED

Error finalize 3ds not authenticated. MPI return one of statuses:

N -The customer failed authentication, and the transaction is denied.
U - Authentication could not be performed due to technical or other problems.

ERROR_NO_3DS_AUTHORIZATION

Error no 3ds authorization, when User authenticates successfully but after 15 minutes or User doesn’t authenticate.

ERROR_MPI_STATUS_TO_LOW: Initialize/Finalize: U/N

Error occurs, when merchant configuration allows only for attempted or full authenticated 3DS transactions with mpi status 'A' or 'Y' but mpi service has returned other status e.g. 'N' or 'U' at any stage of the transaction.

ERROR_3DS_INITIALIZE_FAILED

An error occurred while processing initialize 3DS method caused by an error returned by the service provider

ERROR_3DS_FINALIZE_FAILED

An error occurred while processing finalize 3DS method caused by an error returned by the service provider

ERROR_3DS_VERIFY_FAILED

An error occurred while processing verify 3DS method caused by an error returned by the service provider

REJECTED [only for CASH-CARD]

Amount exceeds current merchant deposit limit

ERROR_3DS_VERSION_NOT_ENROLLED

Merchant has configured a different version of 3DS than specified in the request

ERROR_MPI2_INTERNAL_ERROR

Some unrecognized, internal error occurred in MPI2 service

ERROR_3DS_2_X_REQUIRED_DATA_NOT_COMPLETE

Required configuration data of Merchant are not complete to finish 3DS 2.X process

ERROR_3DS_2_X_CARD_FLOW_INVOKED_FOR_OTHER_CARD_NUMBER_THAN_SPECIFIED_IN_THE_REQUEST

TransactionXId is invalid for card number specified in the request, 3DS 2.X flow invoked for other card number than specified in the request

ERROR_3DS_2_X_CARD_FLOW_INVOKED_FOR_OTHER_MERCHANT_THAN_SPECIFIED_IN_THE_REQUEST

TransactionXId is invalid for merchant specified in the request, 3DS 2.X flow invoked for other merchant than specified in the request

ERROR_3DS_2_X_NOT_FOUND_CARD_AUTHENTICATION_BY_TRANSACTION_XID

Card not found by transactionXId

ERROR_3DS_2_X_CARD_AUTHENTICATION_DOES_NOT_MATCH_TO_PAYMENT_TYPE

Card authentication does not match to payment type

ERROR_3DS_2_X_FAILED

Error 3DS 2.X processing failed

ERROR_TRANSACTIONS_WITHOUT_3DS_ABOVE_30_EUR

Transactions without 3ds above 30 EUR (the blockade applies only to EU countries)

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

ERROR_CARD_NOT_FOUND

Card was not found

ERROR_DATACORE_CONNECTION

Problem with DC

ERROR_SOMETHING_WRONG

ERROR_SOMETHING_WRONG returned when the check status method is executed means that the details for the indicated transaction could not be retrieved correctly due to an unexpected error. This does not mean that the transaction was rejected by our system. In case of receiving ERROR_SOMETHING_WRONG status, please do not hesitate to notify our support team in order to determine the correctness of the transaction execution and quickly correct the method error.

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE_FOR_PLAIN

This error may occur if card’s country is other than user’s country for USA or CAN transaction for PLAIN model

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE

This error may occur if card’s country is other than user’s country for USA or CAN transaction

ERROR_WHILE_GETTING_COUNTRY_CODE

This error may occur when system could not get card country code. Most often, the error is caused by a missing card in the parameters received from the card provider.

ERROR_WHILE_VALIDATING_PROVINCE_NOT_CORRECT_PROVINCE_CODE

Province code is not valid for USA or CAN transactions. Please update user profile

ERROR_VALIDATION

Some validation error occurred

ERROR_VALIDATION Sender type violates merchant model

This error may occur when merchant tries to make transaction in other model than assigned primarily. For example, if merchant’s model is set as CARD-CARD and then merchant will try to make transaction in CASH-CARD model, will receive error as bellow.

ERROR_VALIDATION_EXPIRY_DATE

Card expired

AMOUNT_IS_TOO_SMALL

The amount sent is too small. Enter a larger amount.

AMOUNT_IS_TOO_HIGH

The amount sent is too high. Enter a lower amount.

ERROR_MERCHANT_FUNDING_CARD_COUNTRY_RESTRICTED

Restricted funding card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_PAYMENT_CARD_COUNTRY_RESTRICTED

Restricted payment card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER

Merchant not support the given card provider, please contact support to check merchant configuration

MERCHANT_CRYPTO_OUTSIDE_EEA_UK_NOT_SUPPORTED

Merchant crypto is not supported outside EEA+UK

ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the receiver card country.

ERROR_FUNDING_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the sender card country.

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

ERROR_TRANSACTION_PROCESSING_TIME_TOO_LONG

Processing time of transaction was too long, transaction is declined.

MASTERCARD_MAC_TPE_EXCELLENCE_RULE

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days.

INCORRECT_NAME_DATA

Transaction rejected, sender or receiver name contains fraudulent phrase.

ERROR_NAME_VERIFICATION

Transaction rejected, suspicious sender or receiver name.

3.2.4. Check detailed status

GET /client/send-money-3ds/details/{orderId}, Authentication: Basic Auth
The method allows obtaining a detailed status of 3ds transaction specified by order-id. Parameter order-id was returned in the previous step (Send money multicurrency 3DS).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 8. /client/send-money-3ds/details/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money-3ds/details/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

404 NOT FOUND

Returned when a transaction related to the given orderId doesn’t exist.

422 UNPROCESSABLE ENTITY

Returned when user provides wrong order-id or transaction was failed or was Declined.

500 INTERNAL SERVER ERROR

Returned when an internal error occur.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1022

{
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "APPROVED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

createdDate

String

Date of transaction.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

404 NOT FOUND
HTTP/1.1 404 Not Found
Content-Type: application/json
Content-Length: 51

{
  "errorStatus" : "ERROR_TRANSACTION_NOT_FOUND"
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

422 UNPROCESSABLE ENTITY
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1150

{
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "DECLINED",
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:24.932",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

createdDate

String

Date of transaction.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

The code of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 69

{
  "errorStatus" : "ERROR_SOMETHING_WRONG - Something went wrong."
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

3.2.5. Transaction history

GET /client/{clientId}/transactions?page=0&size=100 Content Type: application/json, Authorization: Basic Auth
Method return page with list of user transactions. Transactions are filtered by clientId provided in GET parameter.
User can send additional optional parameters (page, size) to obtain given page with defined size.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
GET /client/0/transactions?fromDate=2018-03-06&toDate=2018-03-08&page=0&size=100 HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned list of transactions history.

404 NOT FOUND

Returning the list failed.

Example Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1118

{
  "content" : [ {
    "correlationId" : "75044f09-20cf-4508-93e2-2820e5a932f8",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverFirstName" : "Patrick",
    "receiverLastName" : "Evans",
    "receiverHiddenCardNumber" : "511123******1234",
    "receiverProvider" : "MASTERCARD",
    "receiverBankName" : "Bank Polska Kasa Opieki Spółka Akcyjna",
    "receiverEmail" : "receiver@fenige.pl",
    "receiverPhone" : "600300200",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "OUTGOING",
    "3DS" : false
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system

content.[].createdDate

String

Date of transaction processing

content.[].amount

Number

Transaction amount in pennies

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency

content.[].currency

String

Transaction currency

content.[].cardId

Number

Datacore card id used in transaction (sender card)

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].receiverFirstName

String

Transaction receiver first name

content.[].receiverLastName

String

Transaction receiver last name

content.[].receiverHiddenCardNumber

String

Transaction receiver hidden card number

content.[].receiverProvider

String

VISA or MASTERCARD or MAESTRO

content.[].receiverBankName

String

Transaction receiver card bank name.

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card numbe.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverPhone

String

Transaction receiver phone number

content.[].receiverEmail

String

Transaction receiver email

content.[].status

String

Status of the transaction (approved, reversed)

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false)

totalPages

Number

Total number of all pages

totalElements

Number

Total number of all transactions

numberOfElements

Number

Number of transactions on page

first

Boolean

Describes whether the page is first (true ot false)

sort

Object

Details of sort

size

Number

Max number of transactions on page

number

Number

Page number

pageable

String

Page number

404 NOT FOUND
HTTP/1.1 404 Not Found

3.2.6. Transaction details

GET /client/transactions/{orderId} Content Type: application/json, Authorization: Basic Auth
Method return transaction details for single transaction given in method parameter orderId

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
GET /client/transactions/fae3ee90-6f88-4aa6-aff5-7d9f6a5645d3 HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned details of transaction.

Example Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 297

{
  "fundingAmount" : "2.00 PLN",
  "chargedAmount" : "2.04 PLN",
  "commission" : "0.04 PLN",
  "paymentAmount" : "0.54 USD",
  "exchange" : "1.00 PLN = 0.27 USD",
  "transactionTime" : "2018-07-26T17:01:56.364Z",
  "cardIssuer" : "MASTERCARD",
  "amountInUsDollar" : 1,
  "status" : "approved"
}

Response fields

Path Type Description

fundingAmount

String

Funding amount in transaction currency

chargedAmount

String

Charged amount in transaction currency

commission

String

Transaction commission with currency

paymentAmount

String

Payment amount in receiver currency

exchange

String

Revaluation amount from sender to receiver currency

transactionTime

String

Date of the transaction

cardIssuer

String

Card issuer MASTERCARD/VISA

amountInUsDollar

Number

Transaction amount in USD currency in pennies

status

String

Status of transaction approved/reject/decline

3.3. Payouts from deposit

POST /api/v2/client/send-money Content-Type: application/vnd.sendmoney.v2+json, Authorization: Basic Auth, API-TOKEN*
Quick money transfers to debit or credit cards in 150 major currencies. Lower the costs, save time and increase the end-user satisfaction.
Money transfer from Fenige funds deposit to account number is possible from Q1 2024
1 - User by selecting type = RECEIVER defines amount of payment in given currency. This amount is transferred to receiver card in selected currency.
In case there's need revaluation from one currency to another, system uses higherRate for this situation.
For more details about specific rates please refer to Currency Rate method.
*API-TOKEN CASH-PHONE
The API-TOKEN is refreshed each time it is used in the header. The API-TOKEN is refreshed for 30 minutes.
Please notice that you can choose language of email confirmation of this transaction. It is able by attach proper header to request.
SM MULTI CURRENCY
The success of the multicurrency send-money transaction depends primarily on the correctness of the merchant's currency configuration which is done by the admin. To make transactions in a currency other than the currency of the card, contact the admin.
In order to provide users with the ability to safely retry transaction (for example to request for an undelivered response), the v2 of API supports idempotent send money multi-currency operation.
Now on the 'Payouts from deposit' method it is possible to process transactions with Google Pay, Apple Pay, Visa, Mastercard tokens. All you need to do is enter a token in the receiver.cardNumber field. Only for Payouts API!

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

When performing authorization, remember that there are currencies with different number of decimal places. For example: VND has no pennies and KWD has three decimal places. Please take this into account in the Amout field. For more information on other currencies, see ISO 4217.

Worth to note are the new CARD_ACCOUNT and CASH_ACCOUNT transaction models. Using this transaction model, we can quickly make a transfer from a card to an account number or from a Fenige cash deposit to an account number. Transactions in this model are very simple and differ slightly from normal card-to-card transactions. Only the receiver object is changed. An important piece of information to ensure high transaction compliance is the ability to execute the /client/send-money/validate method, which will make sure that your request body is correct and can be processed correctly in a real transaction with the /api/v2/client/send-money method. Your request body will be validate in Visa/Mastercard side so we can be sure that information you gathered is correct. Look at the CASH-ACCOUNT tab

3.3.1. Request

Request fields

Example HTTP Request
CASH-PLAIN
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 676
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "3cc879d8-5281-43c2-9d64-fef413545943",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "CASH",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "personalId" : "AGC688910",
    "country" : "PL"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}

Response fields

Table 9. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender CASH

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver PHONE

CASH-PLAIN with calculate commission result
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 746
Host: java-staging.fenige.pl:8181

{
  "calculateCommissionUuid" : "a0a8223b-8a0e-4c49-84a0-bb91601eccbe",
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "89a85b9e-c72d-44cc-9639-320842820bb8",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "CASH",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "personalId" : "AGC688910",
    "country" : "PL"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}

Response fields

Table 10. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender CASH

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver PHONE

calculateCommissionUuid

String

Optional

@Optional

Unique calculate commission result identifier that allows to use calculated commission in transaction. More information in Calculate commission payout chapter. If calculateCommissionUuid is not provided, commissions will be calculated based on actual currency rates.

CASH-PHONE
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 672
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "47e52243-d7b8-4e6c-a9e2-ec85bbd1e720",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "CASH",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "personalId" : "AGC688910",
    "country" : "PL"
  },
  "receiver" : {
    "type" : "PHONE",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "phoneNumber" : "48123777619",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}

Response fields

Table 11. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender CASH

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver PHONE

CASH-ACCOUNT
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1003
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "ee2f6733-803d-4e1b-a3db-e60c09ace5a5",
  "transactionId" : "TRX220132AM",
  "description" : "Test Account transaction",
  "sender" : {
    "type" : "CASH",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "personalId" : "AGC688910",
    "country" : "PL"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}

Response fields

Table 12. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender CASH

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver PHONE

CASH-ACCOUNT (Validation)
POST /client/send-money/validate HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 957
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "type" : "RECEIVER",
  "requestId" : "32a99272-6e82-47ea-b034-c571dcc5ac45",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "CASH",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "personalId" : "AGC688910",
    "country" : "PL"
  },
  "receiver" : {
    "type" : "ACCOUNT",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2023-12-13",
    "currency" : "PLN",
    "bank" : {
      "bankCode" : "800554",
      "bankCodeType" : "SORT_CODE",
      "bankName" : "Barclays",
      "accountName" : "Money Market",
      "accountNumber" : "BE71096123456769",
      "accountNumberType" : "IBAN",
      "countryCode" : "BE",
      "currencyCode" : "EUR"
    },
    "accountType" : "I",
    "countryOfResidence" : "PL"
  }
}

Response fields

Table 13. Multicurrency
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender CASH

receiver

Object

Required

@NotNull

Receiver PLAIN Receiver CASH Receiver PHONE

3.3.2. Response

Response status
Status Description

200 OK - Error validation

Returned list of field name which has validation errors.

202 Accepted

- Returned when the transaction with the provided requestId has been registered in the system, but has not yet been completed. The user can retry in a few seconds to get the transaction result. Response body: Empty
or
- Returned order-id when transaction will be processed.

400 Bad Request

Returned e.g. when a different transaction with the provided requestId has already been registered in the system.

401 Unauthorized

Returned when API-TOKEN was broken.

Example HTTP Response
202 Accepted
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 56

{
  "orderId" : "846647ee-8268-4e5d-8a4a-64267834ed1b"
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier

400 Bad request
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 104

{
  "error" : {
    "message" : "Another transaction with the same id has already been processed."
  }
}
200 OK - Error validation
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
	"status": "ERROR_VALIDATION",
	"error": {
		"message": "Some information is missing or incorrect.",
		"errors": [{
				"field": "requestId",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "cvc2",
				"message": [
					"may not be null",
					"length must be 3"
				]
			},
			{
				"field": "type",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "amount",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
				"field": "sender.expirationDate",
				"message": [
					"invalid card expiration date",
					"may not be null",
					"may not be empty"
				]
			},
			{
				"field": "sender.city",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 25"
				]
			},
			{
				"field": "sender.street",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 50"
				]
			},
            {
				"field": "sender.postalCode",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10"
				]
			},
            {
                "field": "sender.flatNumber",
                "message": [
                    "must be null",
                    "length must be between 0 and 5"
                ]
            },
			{
				"field": "sender.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.houseNumber",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10",
                    "must match the expression: ^[1-9][0-9]{0,4}(?:[A-z]?[0-9]{0,4})?((?:[-/ ][1-9]?[A-z]?[0-9]{0,4})*[A-z]?)?$"
				]
			},
			{
				"field": "sender.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
            {
				"field": "sender.email",
				"message": [
					"may not be empty",
					"may not be null",
					"not a well-formed email address",
					"lenght must be beetween 1 and 128"
				]
			},
			{
				"field": "receiver",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.currency",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
                "field": "sender",
                "message": [
                     "province is mandatory only if country code is US or CA"
                ]
            },
            {
                "field": "sender.province",
                "message": [
                      "is not correct province code for country code US",
                      "may not be null"
                ]
            },
            {
                "field": "sender.province",
                 "message": [
                       "may not be null",
                       "is not correct province code for country code CA"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                        "must match ^[A-Z]{2}$",
                        "is not correct province code for country code US"
                 ]
            },
            {
                 "field": "sender.currency",
                 "message": [
                       "Currency is not supported"
                ]
            },
            {
                 "field": "receiver.currency",
                 "message": [
                       "Currency is not supported"
                ]
            }
		]
	}
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_API_TOKEN_NOT_FOUND",
    "error": {
        "message": "API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver."
    }
}
401 UNAUTHORIZED
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "Username or password is not correct",
      "path": "/api/v2/client/send-money"
}
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "ERROR_USER_NOTFOUND",
      "path": "/api/v2/client/send-money"
}
Table 14. Response fields
Path Description

timestamp

Time when request was executed

status

Http response code

error

Http status name

message

Message for response code

path

Path to a specific resource

403 FORBIDDEN
HTTP Response - Error
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
    "timestamp": 1610464313387,
    "status": 403,
    "error": "Forbidden",
    "message": "No message available",
    "path": "/client/send-money-3ds"
}

3.3.3. Calculate commission payout

POST /client/calculate-commission/payout, Authentication: Basic Auth
This method is used to receive information about the commission that will be charged for the transaction. Merchant has to specify in the field: type two values (SENDER OR RECEIVER). After selecting the value: "SENDER", the transaction will be sent in the amount indicated in the field: amount. Whereas after choosing the value: "RECEIVER", the transaction will be received in the amount indicated in the field: amount. For Payouts the value must be RECEIVER. The method allows merchant to calculate commissions for the currencies that have been entered. Result of this method can be used in transaction by passing calculateCommissionUuid from the response.
Request
CASH-PLAIN
POST /client/calculate-commission/payout HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 189
Host: java-staging.fenige.pl:8181

{
  "amount" : 100,
  "type" : "RECEIVER",
  "sender" : {
    "type" : "CASH"
  },
  "receiver" : {
    "type" : "PLAIN",
    "cardNumber" : "5575167825713507",
    "currency" : "PLN"
  }
}
Table 15. Calculate commission request fields
Path Type Validation Rule Description

amount

Number

Required

@NotNull, @Min(100)

The total transfer amount (in pennies)

type

String

Required

@NotNull

Value for specific transaction type. Must be RECEIVER

sender

Object

Required

@NotNull

Required configuration per request. Must be CASH type.

receiver

Object

Required

@NotNull

Required configuration per request (PLAIN RECEIVER, PHONE RECEIVER)

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 186

{
  "calculateCommissionUuid" : "9e779924-2e34-49e1-b55f-d4c947282b71",
  "depositChargeAmount" : 200,
  "depositChargeCurrency" : "PLN",
  "calculateCommissionExpiration" : 1718724018
}

Response fields

Path Type Description

calculateCommissionUuid

String

Unique identifier that can be used in authorization to use calculate commission result.

depositChargeAmount

Number

Amount that will be charged from deposit in pennies

depositChargeCurrency

String

Deposit currency

calculateCommissionExpiration

Number

Expiration date of calculate commission result in unix time

422 Unprocessable entity
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 184

{
  "status" : "E0152",
  "message" : "Transaction rejected, issuer card not supported",
  "httpStatus" : "UNPROCESSABLE_ENTITY",
  "traceId" : "e32aa27f-dbac-4265-8146-ac0f9425e288"
}

Response fields

Path Type Description

traceId

String

Trace identifier

status

String

Response code from Fenige system

message

String

Message for response code from Fenige system

httpStatus

String

Response http status

500 Internal server error
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 150

{
  "status" : "E9000",
  "message" : "Domain error",
  "httpStatus" : "INTERNAL_SERVER_ERROR",
  "traceId" : "585479e5-5b63-4d8a-ab01-552673cfb7af"
}

Response fields

Path Type Description

traceId

String

Trace identifier

status

String

Response code from Fenige system

message

String

Message for response code from Fenige system

httpStatus

String

Response http status

3.3.4. Check status

GET /client/send-money/{orderId}, Authentication: Basic Auth
The method allows obtaining a status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 16. /client/send-money/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

500 INTERNAL SERVER ERROR

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1260

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH",
    "hiddenCardNumber" : "****************",
    "bankName" : ""
  },
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1

PAYMENT_TRANSACTION_DECLINED:CODE_05

After receiving these statuses, the transaction was rejected

Error statuses

Name Description

FUNDING_TRANSACTION_DECLINED:CODE_XX, PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

ISSUER_NOT_SUPPORTED

This card is not supported

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

ERROR_FUNDING_BANK_IS_BLOCKED

Funding bank is blocked in Fenige

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

FUNDING_TRANSACTION_DECLINED:ACQ_ERROR [only for CARD-CARD]

Funding transaction was declined and payment not send

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

AML_ERROR

User was found on the stop list

NETWORK_ERROR

Acceptance network is unavailable

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

CURRENCY_NOT_SUPPORTED

Currency is not supported

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

ERROR_WEEKLY_TRANSACTION_LIMIT

Weekly transaction limit for amount per card exceeded

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_SENDER_CARD_IS_BLOCKED [only for CARD-CARD]

Sender’s card is blocked

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

ERROR_SENDER_USER_IS_BLOCKED [only for CARD-CARD]

User acting as sender is blocked

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

ERROR_SENDER_BIN_IS_BLOCKED [only for CARD-CARD]

BIN of sender’s card is blocked

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

ERROR_MONITORING

Some unrecognized error occurred

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

FUNDING_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

FUNDING_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION [only for CARD-CARD]

Funding process failed and it is need to manual verification of transaction

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

FUNDING_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip_proxy response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

REJECTED [only for CASH-CARD]

Amount exceeds current merchant deposit limit

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

ERROR_CARD_NOT_FOUND

Card was not found

ERROR_DATACORE_CONNECTION

Problem with DC

ERROR_SOMETHING_WRONG

ERROR_SOMETHING_WRONG returned when the check status method is executed means that the details for the indicated transaction could not be retrieved correctly due to an unexpected error. This does not mean that the transaction was rejected by our system. In case of receiving ERROR_SOMETHING_WRONG status, please do not hesitate to notify our support team in order to determine the correctness of the transaction execution and quickly correct the method error.

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE_FOR_PLAIN

This error may occur if card’s country is other than user’s country for USA or CAN transaction for PLAIN model

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE

This error may occur if card’s country is other than user’s country for USA or CAN transaction

ERROR_WHILE_GETTING_COUNTRY_CODE

This error may occur when system could not get card country code. Most often, the error is caused by a missing card in the parameters received from the card provider.

ERROR_WHILE_VALIDATING_PROVINCE_NOT_CORRECT_PROVINCE_CODE

Province code is not valid for USA or CAN transactions. Please update user profile

ERROR_VALIDATION

Some validation error occurred

ERROR_VALIDATION Sender type violates merchant model

This error may occur when merchant tries to make transaction in other model than assigned primarily. For example, if merchant’s model is set as CARD-CARD and then merchant will try to make transaction in CASH-CARD model, will receive error as bellow.

ERROR_VALIDATION_EXPIRY_DATE

Card expired

AMOUNT_IS_TOO_SMALL

The amount sent is too small. Enter a larger amount.

AMOUNT_IS_TOO_HIGH

The amount sent is too high. Enter a lower amount.

ERROR_MERCHANT_FUNDING_CARD_COUNTRY_RESTRICTED

Restricted funding card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_PAYMENT_CARD_COUNTRY_RESTRICTED

Restricted payment card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER

Merchant not support the given card provider, please contact support to check merchant configuration

MERCHANT_CRYPTO_OUTSIDE_EEA_UK_NOT_SUPPORTED

Merchant crypto is not supported outside EEA+UK

ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the receiver card country.

ERROR_FUNDING_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the sender card country.

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

ERROR_TRANSACTION_PROCESSING_TIME_TOO_LONG

Processing time of transaction was too long, transaction is declined.

MASTERCARD_MAC_TPE_EXCELLENCE_RULE

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days.

INCORRECT_NAME_DATA

Transaction rejected, sender or receiver name contains fraudulent phrase.

ERROR_NAME_VERIFICATION

Transaction rejected, suspicious sender or receiver name.

ERROR_TRANSACTION_REJECTED_COUNTRY_OF_RESIDENCE_NOT_PERMITTED

Transaction rejected, card country is not supported for merchants crypto.

ERROR_SENDER_COUNTRY_IS_REQUIRED

Transaction card-account rejected, country code in sender object is required for this transactional model

ERROR_SENDER_PERSONAL_ID_IS_REQUIRED

Transaction card-account or cash account rejected, personalId field in sender object is required for this transactional model

ERROR_MERCHANT_OR_CARD_COUNTRY_SAME_AS_RECEIVER_BANK_NOT_PERMITTED

Transaction rejected, country of merchant cannot be the same as receiver’s bank code

3.3.5. Check detailed status

GET /client/send-money/details/{orderId}, Authentication: Basic Auth
    The method allows obtaining a detailed status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money
multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 17. /client/send-money/details/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/details/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

404 NOT FOUND

Returned when a transaction related to the given orderId doesn’t exist.

422 UNPROCESSABLE ENTITY

Returned when user provides wrong order-id or transaction was failed or was Declined.

500 INTERNAL SERVER ERROR

Returned when an internal error occur.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1230

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH"
  },
  "transactionStatus" : "APPROVED",
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

404 NOT FOUND
HTTP/1.1 404 Not Found
Content-Type: application/json
Content-Length: 51

{
  "errorStatus" : "ERROR_TRANSACTION_NOT_FOUND"
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

422 UNPROCESSABLE ENTITY
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1287

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "DECLINED",
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:25.197",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

Additional data of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

422 UNPROCESSABLE ENTITY CASH-CARD
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1358

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH"
  },
  "transactionStatus" : "DECLINED",
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68,
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:24.637",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

The code of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for declined transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 69

{
  "errorStatus" : "ERROR_SOMETHING_WRONG - Something went wrong."
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

3.4. BLIK to Card

POST /api/v2/client/send-money Content-Type: application/vnd.sendmoney.v2+json, Authorization: Basic Auth, API-TOKEN*
Innovative technology that allows to send money between BLIK and cards instantly anywhere in the world. No SWIFT or bank account number needed!
This method is used to MoneySend transaction (funding and payment). To enable users to make transfers in any currency, Fenige introduces the send-money method for
multicurrency.
1 - User by selecting type = SENDER defines amount of funding in PLN. This amount is collected from sender card in PLN currency.
2 - User by selecting type = RECEIVER defines amount of payment in given currency. This amount is transferred to receiver card in selected currency.
In case there's need revaluation from one currency to another, system uses lowerRate for situation 1 and higherRate for situation 2.
For more details about specific rates please refer to Currency Rate method.
TIP: Please notice that you can choose language of email confirmation of this transaction. It is able by attach proper header to request.
SM MULTI CURRENCY
The success of the multicurrency send-money transaction depends primarily on the correctness of the merchant's currency configuration which is done by the admin. To make transactions in a currency other than the currency of the card, contact the admin.
In order to provide users with the ability to safely retry transaction (for example to request for an undelivered response), the v2 of API supports idempotent send money multi-currency operation.
To use the BLIK to card transfer service, you will need to have a mobile banking app from one of the participating banks. Follow the instructions on the app to complete the transfer. Once you have confirmed the transaction, the money
will be transferred to the card instantly.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

When performing authorization, remember that there are currencies with different number of decimal places. For example: VND has no pennies and KWD has three decimal places. Please take this into account in the Amout field. For more information on other currencies, see ISO 4217.

3.4.1. Request

Request fields

Table 18. Blik
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies)

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

requestId

String

Required

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

transactionId

String

Optional

@Length(max = 64)

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method.

sender

Object

Required

@NotNull

Sender BLIK

receiver

Object

Required

@NotNull

Receiver PLAIN

Example HTTP Request
BLIK-PLAIN
POST /api/v2/client/send-money HTTP/1.1
Content-Type: application/vnd.sendmoney.v2+json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1207
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "requestId" : "82d3253e-ebe7-4253-9361-c60acf1fbf42",
  "transactionId" : "TRX220132AM",
  "sender" : {
    "type" : "BLIK",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "country" : "PL",
    "personalId" : "AGC688910",
    "currency" : "PLN",
    "firstDescriptionLine" : "Shop description",
    "secondDescriptionLine" : "Second line of description",
    "thirdDescriptionLine" : "Third line of description",
    "fourthDescriptionLine" : "https://ecom-staging.fenige.pl/",
    "redirectUrlAuthorized" : "https://ecom-staging.fenige.pl/transaction/authorized",
    "redirectUrlDenied" : "https://ecom-staging.fenige.pl/transaction/denied"
  },
  "receiver" : {
    "type" : "PLAIN",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "currency" : "PLN",
    "countryOfResidence" : "PL"
  }
}

3.4.2. Response

Response status
Status Description

200 OK - Error validation

Returned list of field name which has validation errors.

202 Accepted

- Returned when the transaction with the provided requestId has been registered in the system, but has not yet been completed. The user can retry in a few seconds to get the transaction result. Response body: Empty
or
- Returned order-id when transaction will be processed.

400 Bad Request

Returned e.g. when a different transaction with the provided requestId has already been registered in the system.

401 Unauthorized

Returned when API-TOKEN was broken.

Example HTTP Response
202 Accepted BLIK
HTTP/1.1 202 Accepted
Content-Type: application/json
Content-Length: 1261

{
  "orderId" : "2d868491-ce01-401b-955d-a4b15b60f367",
  "base64Form" : "PGh0bWw+PFNDUklQVCBMQU5HVUFHRT0iSmF2YXNjcmlwdCI+ZnVuY3Rpb24gT25Mb2FkRXZlbnQoKSB7ZG9jdW1lbnQuZG93bmxvYWRGb3JtLnN1Ym1pdCgpO308L1NDUklQVD48Ym9keSBPbkxvYWQ9Ik9uTG9hZEV2ZW50KCk7Ij48Zm9ybSBuYW1lPSJkb3dubG9hZEZvcm0iIGFjY2VwdC1jaGFyc2V0PSJJU08tODg1OS0yIiBhY3Rpb249Imh0dHBzOi8vMTkzLjI3LjYuMjI1L2JsaWt3ZWIvdHJhbnNhY3Rpb24vdHJhbnNhY3Rpb25faW5pdC9zdWJtaXQiIG1ldGhvZD0iUE9TVCI+PElOUFVUIHR5cGU9ImhpZGRlbiIgbmFtZT0iVHlwZSIgdmFsdWU9IklwYXkyIj48SU5QVVQgdHlwZT0iaGlkZGVuIiBuYW1lPSJNZXJjaGFudElEIiB2YWx1ZT0iMTcxOTUiPjxJTlBVVCB0eXBlPSJoaWRkZW4iIG5hbWU9IkN1cnJlbmN5IiB2YWx1ZT0iUExOIj48SU5QVVQgdHlwZT0iaGlkZGVuIiBuYW1lPSJBbW91bnQiIHZhbHVlPSIxMDAwIj48SU5QVVQgdHlwZT0iaGlkZGVuIiBuYW1lPSJDdXN0b21QYXJhbSIgdmFsdWU9Ijg0MGY1ZjYzOGY0OTQwNGZiMGU1OGQwMDU1NTg1NzM4Ij48SU5QVVQgdHlwZT0iaGlkZGVuIiBuYW1lPSJEZXNjcmlwdGlvbiIgdmFsdWU9ImV4YW1wbGV8ZGVzY3JpcHRpb258w7PEhcWbxIfFm8SFfCI+PElOUFVUIHR5cGU9ImhpZGRlbiIgbmFtZT0iVGltZXN0YW1wIiB2YWx1ZT0iMjAyMi0wNi0yOVQxNTo0MDo1OC4zMjIrMDI6MDAiPjxJTlBVVCB0eXBlPSJoaWRkZW4iIG5hbWU9Ik1DQyIgdmFsdWU9IjA3NDIiPjxJTlBVVCB0eXBlPSJoaWRkZW4iIG5hbWU9IkNvbnRyb2xEYXRhIiB2YWx1ZT0iZDkyZjI2MTI1NmQwMWNiNjU4ZWI3MzIwZDczNDE2MjYyOGNhOTViNzRmYWRmY2UxOGFmMDliMDdkOWIwOGNjMCI+PC9mb3JtPjwvYm9keT48L2h0bWw+"
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier

base64Form

String

HTML page encoded base64 that includes all necessary data that has to be send to BLIK. Page can be simply decoded and used for making transactions.

400 Bad request
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 104

{
  "error" : {
    "message" : "Another transaction with the same id has already been processed."
  }
}
200 OK - Error validation
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
	"status": "ERROR_VALIDATION",
	"error": {
		"message": "Some information is missing or incorrect.",
		"errors": [{
				"field": "requestId",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "cvc2",
				"message": [
					"may not be null",
					"length must be 3"
				]
			},
			{
				"field": "type",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "amount",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
				"field": "sender.expirationDate",
				"message": [
					"invalid card expiration date",
					"may not be null",
					"may not be empty"
				]
			},
			{
				"field": "sender.city",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 25"
				]
			},
			{
				"field": "sender.street",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 50"
				]
			},
            {
				"field": "sender.postalCode",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10"
				]
			},
            {
                "field": "sender.flatNumber",
                "message": [
                    "must be null",
                    "length must be between 0 and 5"
                ]
            },
			{
				"field": "sender.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.houseNumber",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10",
                    "must match the expression: ^[1-9][0-9]{0,4}(?:[A-z]?[0-9]{0,4})?((?:[-/ ][1-9]?[A-z]?[0-9]{0,4})*[A-z]?)?$"
				]
			},
			{
				"field": "sender.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
            {
				"field": "sender.email",
				"message": [
					"may not be empty",
					"may not be null",
					"not a well-formed email address",
					"lenght must be beetween 1 and 128"
				]
			},
			{
				"field": "receiver",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "receiver.currency",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
                "field": "sender",
                "message": [
                     "province is mandatory only if country code is US or CA"
                ]
            },
            {
                "field": "sender.province",
                "message": [
                      "is not correct province code for country code US",
                      "may not be null"
                ]
            },
            {
                "field": "sender.province",
                 "message": [
                       "may not be null",
                       "is not correct province code for country code CA"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                        "must match ^[A-Z]{2}$",
                        "is not correct province code for country code US"
                 ]
            },
            {
                 "field": "sender.currency",
                 "message": [
                       "Currency is not supported"
                ]
            },
            {
                 "field": "receiver.currency",
                 "message": [
                       "Currency is not supported"
                ]
            }
		]
	}
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_API_TOKEN_NOT_FOUND",
    "error": {
        "message": "API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver."
    }
}
401 UNAUTHORIZED
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "Username or password is not correct",
      "path": "/api/v2/client/send-money"
}
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "ERROR_USER_NOTFOUND",
      "path": "/api/v2/client/send-money"
}
Table 19. Response fields
Path Description

timestamp

Time when request was executed

status

Http response code

error

Http status name

message

Message for response code

path

Path to a specific resource

403 FORBIDDEN
HTTP Response - Error
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
    "timestamp": 1610464313387,
    "status": 403,
    "error": "Forbidden",
    "message": "No message available",
    "path": "/client/send-money-3ds"
}

3.4.3. BLIK

General information

BLIK is a popular mobile payment system, enabling users to carry out secure transactions using their smartphones. Integrated within banking apps, BLIK allows for online and in-store payments, ATM withdrawals, and more, through a generated six-digit code, making financial transactions swift and straightforward.

How does it work

Customer choose the BLIK payment method, in order to complete the transaction he has to provide a BLIK code from bank application. The BLIK code is a one-off, 6-digit code, it is valid for 2 minutes. After that time, new one has to be generated. When code is provide it has to be also confirmed in bank app and that ends the transaction.

Example BLIK payment form

eblik payment form

For development purposes, please note the following special rule for BLIK codes: Use codes that begin with "777 xxx", to process payment successfully. For codes that begin with any other number, the transaction will be rejected.

3.4.4. Check status

GET /client/send-money/{orderId}, Authentication: Basic Auth
The method allows obtaining a status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 20. /client/send-money/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

500 INTERNAL SERVER ERROR

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1123

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  }
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

200 OK CASH-CARD
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1260

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH",
    "hiddenCardNumber" : "****************",
    "bankName" : ""
  },
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1

PAYMENT_TRANSACTION_DECLINED:CODE_05

After receiving these statuses, the transaction was rejected

Error statuses

Name Description

FUNDING_TRANSACTION_DECLINED:CODE_XX, PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

ISSUER_NOT_SUPPORTED

This card is not supported

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

ERROR_FUNDING_BANK_IS_BLOCKED

Funding bank is blocked in Fenige

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

FUNDING_TRANSACTION_DECLINED:ACQ_ERROR [only for CARD-CARD]

Funding transaction was declined and payment not send

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

AML_ERROR

User was found on the stop list

NETWORK_ERROR

Acceptance network is unavailable

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

CURRENCY_NOT_SUPPORTED

Currency is not supported

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

ERROR_WEEKLY_TRANSACTION_LIMIT

Weekly transaction limit for amount per card exceeded

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_SENDER_CARD_IS_BLOCKED [only for CARD-CARD]

Sender’s card is blocked

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

ERROR_SENDER_USER_IS_BLOCKED [only for CARD-CARD]

User acting as sender is blocked

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

ERROR_SENDER_BIN_IS_BLOCKED [only for CARD-CARD]

BIN of sender’s card is blocked

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

ERROR_MONITORING

Some unrecognized error occurred

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

FUNDING_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

FUNDING_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION [only for CARD-CARD]

Funding process failed and it is need to manual verification of transaction

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

FUNDING_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT [only for CARD-CARD]

Funding transaction declined - mip_proxy response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

REJECTED [only for CASH-CARD]

Amount exceeds current merchant deposit limit

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

ERROR_CARD_NOT_FOUND

Card was not found

ERROR_DATACORE_CONNECTION

Problem with DC

ERROR_SOMETHING_WRONG

ERROR_SOMETHING_WRONG returned when the check status method is executed means that the details for the indicated transaction could not be retrieved correctly due to an unexpected error. This does not mean that the transaction was rejected by our system. In case of receiving ERROR_SOMETHING_WRONG status, please do not hesitate to notify our support team in order to determine the correctness of the transaction execution and quickly correct the method error.

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE_FOR_PLAIN

This error may occur if card’s country is other than user’s country for USA or CAN transaction for PLAIN model

ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE

This error may occur if card’s country is other than user’s country for USA or CAN transaction

ERROR_WHILE_GETTING_COUNTRY_CODE

This error may occur when system could not get card country code. Most often, the error is caused by a missing card in the parameters received from the card provider.

ERROR_WHILE_VALIDATING_PROVINCE_NOT_CORRECT_PROVINCE_CODE

Province code is not valid for USA or CAN transactions. Please update user profile

ERROR_VALIDATION

Some validation error occurred

ERROR_VALIDATION Sender type violates merchant model

This error may occur when merchant tries to make transaction in other model than assigned primarily. For example, if merchant’s model is set as CARD-CARD and then merchant will try to make transaction in CASH-CARD model, will receive error as bellow.

ERROR_VALIDATION_EXPIRY_DATE

Card expired

AMOUNT_IS_TOO_SMALL

The amount sent is too small. Enter a larger amount.

AMOUNT_IS_TOO_HIGH

The amount sent is too high. Enter a lower amount.

ERROR_MERCHANT_FUNDING_CARD_COUNTRY_RESTRICTED

Restricted funding card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_PAYMENT_CARD_COUNTRY_RESTRICTED

Restricted payment card country was used. + This error may occur when a merchant uses a sender card issued in a country that is on the list of countries High Risk or country not allowed to perform transactions in Fenige API. Please contact support.

ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER

Merchant not support the given card provider, please contact support to check merchant configuration

MERCHANT_CRYPTO_OUTSIDE_EEA_UK_NOT_SUPPORTED

Merchant crypto is not supported outside EEA+UK

ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the receiver card country.

ERROR_FUNDING_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the sender card country.

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

ERROR_TRANSACTION_PROCESSING_TIME_TOO_LONG

Processing time of transaction was too long, transaction is declined.

MASTERCARD_MAC_TPE_EXCELLENCE_RULE

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days.

INCORRECT_NAME_DATA

Transaction rejected, sender or receiver name contains fraudulent phrase.

ERROR_NAME_VERIFICATION

Transaction rejected, suspicious sender or receiver name.

ERROR_TRANSACTION_REJECTED_COUNTRY_OF_RESIDENCE_NOT_PERMITTED

Transaction rejected, card country is not supported for merchants crypto.

ERROR_SENDER_COUNTRY_IS_REQUIRED

Transaction card-account rejected, country code in sender object is required for this transactional model

ERROR_SENDER_PERSONAL_ID_IS_REQUIRED

Transaction card-account or cash account rejected, personalId field in sender object is required for this transactional model

ERROR_MERCHANT_OR_CARD_COUNTRY_SAME_AS_RECEIVER_BANK_NOT_PERMITTED

Transaction rejected, country of merchant cannot be the same as receiver’s bank code

3.4.5. Check detailed status

GET /client/send-money/details/{orderId}, Authentication: Basic Auth
    The method allows obtaining a detailed status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money
multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 21. /client/send-money/details/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/details/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

404 NOT FOUND

Returned when a transaction related to the given orderId doesn’t exist.

422 UNPROCESSABLE ENTITY

Returned when user provides wrong order-id or transaction was failed or was Declined.

500 INTERNAL SERVER ERROR

Returned when an internal error occur.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1159

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "APPROVED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

200 OK CASH-CARD
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1230

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH"
  },
  "transactionStatus" : "APPROVED",
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

203 NON-AUTHORITATIVE INFORMATION
HTTP/1.1 203 Non-Authoritative Information

After you get 203 you need to check status in a while because we processing this transaction and if you don’t get a response (200 - succeeded or 500 - declined) within 60 seconds then please contact us.

404 NOT FOUND
HTTP/1.1 404 Not Found
Content-Type: application/json
Content-Length: 51

{
  "errorStatus" : "ERROR_TRANSACTION_NOT_FOUND"
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

422 UNPROCESSABLE ENTITY
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1287

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "DECLINED",
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:25.197",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

Additional data of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

422 UNPROCESSABLE ENTITY CASH-CARD
HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json
Content-Length: 1358

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : false,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "CASH"
  },
  "transactionStatus" : "DECLINED",
  "merchantSettlementCurrency" : "USD",
  "fenigeCommissionInMerchantSettlementCurrency" : 0.05,
  "transactionAmountInMerchantSettlementCurrency" : 2.68,
  "cardBlockType" : "TEMP",
  "cardBlockedUntil" : "2024-06-19T17:20:24.637",
  "errorStatus" : "ERROR_SENDER_CARD_IS_BLOCKED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

merchantSettlementCurrency

String

Merchant settlement currency

fenigeCommissionInMerchantSettlementCurrency

Number

Commission Fenige in merchant settlement currency

transactionAmountInMerchantSettlementCurrency

Number

Transaction amount in merchant settlement currency

transactionStatus

String

Status of the transaction (PENDING, APPROVED, DECLINED, REJECTED, REVERSED)

errorStatus

String

The code of the error occurred during a processing of the request

cardBlockType

String

Card lock type

cardBlockedUntil

String

Card’s lock end date

merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for declined transactions if Mastercard returns this information

RevaluationResult

Path Type Description

revaluationFundingAmount

Long

Amount (in pennies) of funding transaction in fundingCurrency

bigDecimalRevaluationFundingAmount

BigDecimal

Amount of funding transaction in fundingCurrency

fundingCurrency

String

Currency code the same as sender’s card currency

revaluationPaymentAmount

Long

Amount (in pennies) of payment transaction in paymentCurrency

bigDecimalRevaluationPaymentAmount

BigDecimal

Amount of payment transaction in paymentCurrency

paymentCurrency

String

Currency code the same as receiver’s card currency

determineCurrencyRate

Object (DetermineCurrencyRate)

Details about conversion

DetermineCurrencyRate

Path Type Description

from

Long

Currency which was conversion from

to

Long

Resulted currency

currencyRate

BigDecimal

Currency rate

500 INTERNAL SERVER ERROR
HTTP/1.1 500 Internal Server Error
Content-Type: application/json
Content-Length: 69

{
  "errorStatus" : "ERROR_SOMETHING_WRONG - Something went wrong."
}

Response fields

Path Type Description

errorStatus

String

Additional data of the error occurred during a processing of the request

3.5. Delayed payment

Mastercard and Visa requires for intra-European Economic Area (EEA), plus United Kingdom, for which EMV 3DS must be used subsequent to a valid authorization soft decline DE39=65 (Mastercard)/1A(Visa). To perform a transaction for which the card has previously received CODE_65-Mastercard, CODE_1A-VISA, the transaction must be processed with full EMV 3DS (3DS 2.x) and the authentication status must be 'Y'.

Correct flow:

  • 3DS 2.x → Challenge → Authentication status Y → Transaction (Recommended)

soft decline Code 65 EMV 3DS

3.5.1. Delayed Send Money

POST /client/delayed/send-money Content-Type: application/json, Authorization: Basic Auth, API-TOKEN*
The Delayed Send Money functionality provides the ability to perform transactions, where recipient is not known at the time of funding execution.
Transaction in the Send Money system consists of Funding and Payment.
In order to perform the method that request is described below, we can execute Funding (with Payment for some cases**).
Money specified in the request ('amount' field) will be charged from the Sender's card, but these money will be transferred to the Receiver's card when Receiver is known (After Delayed Payment method execution).
In order to make the full flow of the transaction, the Delayed Payment method must be executed. In Delayed Payment methods you should define Receiver of Funding - then transaction will be processed.
*API-TOKEN is required for model when sender is DATACORE type.
**See table below with Delayed Send Money models. You can find there information which model executes only Funding or Funding with Payment at the same time.
The API-TOKEN is refreshed each time it is used in the header. The API-TOKEN is refreshed for 30 minutes.
The maximum time for the execution of Delayed Payment after earlier calling Delayed Send Money is 12 hours. After 12 hours after Funding without Payment, it will be reversed.
There is 3 attempts to execute Delayed Payment after earlier call Delayed Send Money.

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

When performing authorization, remember that there are currencies with different number of decimal places. For example: VND has no pennies and KWD has three decimal places. Please take this into account in the Amout field. For more information on other currencies, see ISO 4217.

Quick tour of Delayed Send Money models
Model Sender Receiver Description Transaction Type

DATACORE_SENDER - DELAYED_RECEIVER

DATACORE

DELAYED

For transactions in this model, we provide the full Sender’s data in the request without card number but with the 'cardId' (card is stored in Fenige Datacenter). The user must get API-TOKEN in the /client/login method. The Receiver’s details are unknown yet, so we are waiting for a Delayed Payment to be made.

Funding or Funding & Payment

PLAIN_SENDER - DELAYED_RECEIVER

PLAIN

DELAYED

For transactions in this model, user must provide all the full Sender data in the request. The Receiver’s details are unknown yet, so we are waiting for a Delayed Payment to be made.

Funding or Funding & Payment

Delayed Send Money Examples
DATACORE_SENDER-DELAYED_RECEIVER_EXISTS_IN_DATABASE
DP DATACORE DELAYED SENDER DELAYED RECEIVER EXISTS
DATACORE_SENDER-DELAYED_RECEIVER_NOT_EXISTS_IN_DATABASE
DP DATACORE DELAYED SENDER DELAYED RECEIVER NOT EXISTS
PLAIN_SENDER-DELAYED_RECEIVER_EXISTS_IN_DATABASE
DP PLAIN DELAYED SENDER DELAYED RECEIVER EXISTS
PLAIN_SENDER-DELAYED_RECEIVER_NOT_EXISTS_IN_DATABASE
DP PLAIN DELAYED SENDER DELAYED RECEIVER NOT EXISTS
Requests
DATACORE_SENDER-DELAYED_RECEIVER(Phone)
POST /client/delayed/send-money HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 939
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "cavvAlgorithm" : "02",
    "authenticationStatus" : "Y",
    "eci" : "02",
    "transactionXId" : "91619a55-c7ad-4c8e-883c-b68175df327c"
  },
  "requestId" : "1330df01-2c3d-4eca-a2ca-b5836e5916d9",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "phoneNumber" : "48600300200",
    "currency" : "USD"
  }
}
Table 22. Delayed Send Money Request Fields
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

cvc2

String

Required

@Length(min = 3, max = 3)

Sender card cvc2/cvv2.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

requestId

String

Optional

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

sender

Object

Required

@NotNull

Personal data of Sender.

receiver

Object

Required

@NotNull

Personal data of Receiver.

outside3ds.cavv

String

Required

@NotNull

Cardholder Authentication Verification Value.

outside3ds.eci

String

Required

@NotNull

Electronic Commerce Indicator: 5 (Visa) or 2 (SecureCode) - The cardholder was successfully authenticated. 6 (Visa) or 1 (SecureCode) - Authentication was attempted, but the cardholder was not enrolled. Chargeback protection applies.

outside3ds.authenticationStatus

String

Required

@NotNull

Authentication status. If AuthenticationStatus is "Y" or "A" then outside 3ds flow will be execute.

outside3ds.transactionXId

String

Optional

@NotNull

Cardholder Authentication Verification Value. The transactionXId is the field that defines the 3DS version. The presence of this field in the HTTP request specifies that the transaction will be processed with 3DS 2.X. TransactionXId can be obtained by executing the /authentication method.

outside3ds.cavvAlgorithm

String

Optional

@Optional

Indicates the algorithm used to generate the AuthenticationCAVV value 0 - HMAC 1 - CVV 2 - CVV with ATN 3 - MasterCard SPA algorithm.

DATACORE_SENDER-DELAYED_RECEIVER(Email)
POST /client/delayed/send-money HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
API-TOKEN: d94NYa+xqRrazUPzSgYeJ6qR/MzIOb3IzePb7t9sWds=
Content-Length: 945
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "cavvAlgorithm" : "02",
    "authenticationStatus" : "Y",
    "eci" : "02",
    "transactionXId" : "b093a69f-f950-4b47-8e7d-026ea3f64d60"
  },
  "requestId" : "37252eac-a262-48d8-b4d4-5e6b442763f3",
  "sender" : {
    "type" : "DATACORE",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardId" : 1234,
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "currency" : "USD"
  }
}
Table 23. Delayed Send Money Request Fields
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

cvc2

String

Required

@Length(min = 3, max = 3)

Sender card cvc2/cvv2.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

requestId

String

Optional

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

sender

Object

Required

@NotNull

Personal data of Sender.

receiver

Object

Required

@NotNull

Personal data of Receiver.

outside3ds.cavv

String

Required

@NotNull

Cardholder Authentication Verification Value.

outside3ds.eci

String

Required

@NotNull

Electronic Commerce Indicator: 5 (Visa) or 2 (SecureCode) - The cardholder was successfully authenticated. 6 (Visa) or 1 (SecureCode) - Authentication was attempted, but the cardholder was not enrolled. Chargeback protection applies.

outside3ds.authenticationStatus

String

Required

@NotNull

Authentication status. If AuthenticationStatus is "Y" or "A" then outside 3ds flow will be execute.

outside3ds.transactionXId

String

Optional

@NotNull

Cardholder Authentication Verification Value. The transactionXId is the field that defines the 3DS version. The presence of this field in the HTTP request specifies that the transaction will be processed with 3DS 2.X. TransactionXId can be obtained by executing the /authentication method.

outside3ds.cavvAlgorithm

String

Optional

@Optional

Indicates the algorithm used to generate the AuthenticationCAVV value 0 - HMAC 1 - CVV 2 - CVV with ATN 3 - MasterCard SPA algorithm.

PLAIN_SENDER-DELAYED_RECEIVER(Phone)
POST /client/delayed/send-money HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1018
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "cavvAlgorithm" : "02",
    "authenticationStatus" : "Y",
    "eci" : "02",
    "transactionXId" : "0bb2033d-022b-4941-9553-6fbd8ca3d028"
  },
  "requestId" : "e3c1caaf-9505-4fa5-b01e-633d1eb9efd3",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "birthDate" : "2024-05-23",
    "phoneNumber" : "48600300200",
    "currency" : "USD"
  }
}
Table 24. Delayed Send Money Request Fields
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

cvc2

String

Required

@Length(min = 3, max = 3)

Sender card cvc2/cvv2.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

requestId

String

Optional

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

sender

Object

Required

@NotNull

Personal data of Sender.

receiver

Object

Required

@NotNull

Personal data of Receiver.

outside3ds.cavv

String

Required

@NotNull

Cardholder Authentication Verification Value.

outside3ds.eci

String

Required

@NotNull

Electronic Commerce Indicator: 5 (Visa) or 2 (SecureCode) - The cardholder was successfully authenticated. 6 (Visa) or 1 (SecureCode) - Authentication was attempted, but the cardholder was not enrolled. Chargeback protection applies.

outside3ds.authenticationStatus

String

Required

@NotNull

Authentication status. If AuthenticationStatus is "Y" or "A" then outside 3ds flow will be execute.

outside3ds.transactionXId

String

Optional

@NotNull

Cardholder Authentication Verification Value. The transactionXId is the field that defines the 3DS version. The presence of this field in the HTTP request specifies that the transaction will be processed with 3DS 2.X. TransactionXId can be obtained by executing the /authentication method.

outside3ds.cavvAlgorithm

String

Optional

@Optional

Indicates the algorithm used to generate the AuthenticationCAVV value 0 - HMAC 1 - CVV 2 - CVV with ATN 3 - MasterCard SPA algorithm.

PLAIN_SENDER-DELAYED_RECEIVER(Email)
POST /client/delayed/send-money HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 1024
Host: java-staging.fenige.pl:8181

{
  "amount" : 1000,
  "cvc2" : "123",
  "merchantUrl" : "https://fenige.pl/payments",
  "addressIp" : "192.168.0.1",
  "type" : "SENDER",
  "outside3ds" : {
    "cavv" : "jEu04WZns7pbARAApU4qgNdJTag=",
    "cavvAlgorithm" : "02",
    "authenticationStatus" : "Y",
    "eci" : "02",
    "transactionXId" : "08a83479-9b58-4d82-bdb6-56bf7fa9ddf3"
  },
  "requestId" : "3f5ba348-63a0-4ab5-96e0-91512ca63edd",
  "sender" : {
    "type" : "PLAIN",
    "firstName" : "Mark",
    "lastName" : "Smith",
    "street" : "Olszewskiego",
    "houseNumber" : "17A",
    "city" : "Lublin",
    "postalCode" : "20-400",
    "flatNumber" : "2",
    "email" : "senderEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "cardNumber" : "5117964247989169",
    "expirationDate" : "03/26",
    "personalId" : "AGC688910",
    "currency" : "PLN"
  },
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "receiverEmail@fenige.pl",
    "birthDate" : "2024-05-23",
    "currency" : "USD"
  }
}
Table 25. Delayed Send Money Request Fields
Path Type Validation Rule Description

amount

Number

Required

@NotNull, positive

The total transfer amount (in pennies).

cvc2

String

Required

@Length(min = 3, max = 3)

Sender card cvc2/cvv2.

type

String

Required

@NotNull

Transaction in 'SENDER' or 'RECEIVER' currency, for specific transaction type. CARD_CARD: above, CASH_CARD: RECEIVER, CARD_CASH: SENDER.

merchantUrl

String

Required except CASH-PLAIN transactions.

@NotNull except CASH-PLAIN

Merchant identifier such as the business website URL or reverse domain name as presented to the consumer during checkout

addressIp

String

Required except CASH-PLAIN transactions @Must conform to the IPv4 or IPv6 standard.

@NotNull except CASH-PLAIN

The IP address of the order of transaction.

requestId

String

Optional

@NotNull

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

sender

Object

Required

@NotNull

Personal data of Sender.

receiver

Object

Required

@NotNull

Personal data of Receiver.

outside3ds.cavv

String

Required

@NotNull

Cardholder Authentication Verification Value.

outside3ds.eci

String

Required

@NotNull

Electronic Commerce Indicator: 5 (Visa) or 2 (SecureCode) - The cardholder was successfully authenticated. 6 (Visa) or 1 (SecureCode) - Authentication was attempted, but the cardholder was not enrolled. Chargeback protection applies.

outside3ds.authenticationStatus

String

Required

@NotNull

Authentication status. If AuthenticationStatus is "Y" or "A" then outside 3ds flow will be execute.

outside3ds.transactionXId

String

Optional

@NotNull

Cardholder Authentication Verification Value. The transactionXId is the field that defines the 3DS version. The presence of this field in the HTTP request specifies that the transaction will be processed with 3DS 2.X. TransactionXId can be obtained by executing the /authentication method.

outside3ds.cavvAlgorithm

String

Optional

@Optional

Indicates the algorithm used to generate the AuthenticationCAVV value 0 - HMAC 1 - CVV 2 - CVV with ATN 3 - MasterCard SPA algorithm.

Response
Response status
Status Description

200 OK

Delayed Send Money approved for processing and transaction details returned.

200 OK - Error validation

Returned list of field name which has validation errors.

202 Accepted

- Returned when the transaction with the provided requestId has been registered in the system, but has not yet been completed. The user can retry in a few seconds to get the transaction result. Response body: Empty
or
- Returned order-id when transaction will be processed.

400 Bad Request

Returned when request is incorrect, required fields are missing or the values are not valid.

401 Unauthorized

Returned when API-TOKEN was broken.

500 Internal Server Error

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK When receiver is in database
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1080

{
  "amount" : 2000,
  "bigDecimalAmount" : 20.0,
  "commission" : 0,
  "bigDecimalCommission" : 0,
  "orderId" : "34ff4e20-23e2-434d-9c95-5dd2baa83f08",
  "createdDate" : "09-11-2020, 21:12",
  "fundingRrn" : "031420000725",
  "paymentRrn" : "031420000725",
  "transactionStatus" : "APPROVED",
  "responseCode" : "CODE_00",
  "revaluationResult" : {
    "revaluationFundingAmount" : 2000,
    "bigDecimalRevaluationFundingAmount" : 20.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 2000,
    "bigDecimalRevaluationPaymentAmount" : 20.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "Rob",
    "lastName" : "Wring",
    "hiddenCardNumber" : "511796******9169",
    "provider" : "MASTERCARD",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Mark",
    "lastName" : "Smith",
    "hiddenCardNumber" : "511796******9169",
    "provider" : "MASTERCARD",
    "bankName" : "Alior Bank SA"
  },
  "3DS" : true
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier.

transactionStatus

String

Transaction status.

responseCode

String

Response code.

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100].

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100].

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

revaluationResult.revaluationFundingAmount

Number

Amount (in pennies) of funding transaction in fundingCurrency.

revaluationResult.bigDecimalRevaluationFundingAmount

Number

Amount of funding transaction in fundingCurrency.

revaluationResult.fundingCurrency

String

Currency code the same as sender’s card currency.

revaluationResult.revaluationPaymentAmount

Number

Amount (in pennies) of payment transaction in paymentCurrency.

revaluationResult.bigDecimalRevaluationPaymentAmount

Number

Amount of payment transaction in paymentCurrency.

revaluationResult.paymentCurrency

String

Currency code the same as receiver’s card currency.

revaluationResult.determineCurrencyRate.from

String

Currency which was conversion from.

revaluationResult.determineCurrencyRate.to

String

Resulted currency.

revaluationResult.determineCurrencyRate.currencyRate

String

Currency rate.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

200 OK When receiver is unknown
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 943

{
  "amount" : 2000,
  "bigDecimalAmount" : 20.0,
  "commission" : 0,
  "bigDecimalCommission" : 0,
  "orderId" : "9b8b4359-61e6-46fd-9530-a9c8a088b243",
  "createdDate" : "09-11-2020, 21:12",
  "fundingRrn" : "031420000725",
  "transactionStatus" : "APPROVED_WAITING_FOR_RECEIVER",
  "responseCode" : "CODE_00",
  "revaluationResult" : {
    "revaluationFundingAmount" : 2000,
    "bigDecimalRevaluationFundingAmount" : 20.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 2000,
    "bigDecimalRevaluationPaymentAmount" : 20.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "email" : "receiver@fenige.pl"
  },
  "sender" : {
    "firstName" : "Mark",
    "lastName" : "Smith",
    "hiddenCardNumber" : "511796******9169",
    "provider" : "MASTERCARD",
    "bankName" : "Alior Bank SA"
  },
  "3DS" : true
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier.

transactionStatus

String

Transaction status.

responseCode

String

Response code.

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100].

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100].

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

revaluationResult.revaluationFundingAmount

Number

Amount (in pennies) of funding transaction in fundingCurrency.

revaluationResult.bigDecimalRevaluationFundingAmount

Number

Amount of funding transaction in fundingCurrency.

revaluationResult.fundingCurrency

String

Currency code the same as sender’s card currency.

revaluationResult.revaluationPaymentAmount

Number

Amount (in pennies) of payment transaction in paymentCurrency.

revaluationResult.bigDecimalRevaluationPaymentAmount

Number

Amount of payment transaction in paymentCurrency.

revaluationResult.paymentCurrency

String

Currency code the same as receiver’s card currency.

revaluationResult.determineCurrencyRate.from

String

Currency which was conversion from.

revaluationResult.determineCurrencyRate.to

String

Resulted currency.

revaluationResult.determineCurrencyRate.currencyRate

String

Currency rate.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

400 Bad request
HTTP/1.1 400 Bad Request
Content-Type: application/json
Content-Length: 104

{
  "error" : {
    "status" : "ERROR_INVALID_JSON",
    "message" : "Some properties are invalid"
  }
}
500 Internal Server Error
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1
{
    “status”: “ERROR_FUNDING_FAILED”,
    “error”: {
        “message”: “FUNDING_TRANSACTION_DECLINED:CODE_05”
    }
}

After receiving these statuses, the transaction was rejected

Error statuses

Name Description

FUNDING_TRANSACTION_DECLINED:CODE_XX, PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

ISSUER_NOT_SUPPORTED

This card is not supported

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

ERROR_API_TOKEN_NOT_FOUND

API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

ERROR_FUNDING_BANK_IS_BLOCKED

Funding bank is blocked in Fenige

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

FUNDING_TRANSACTION_DECLINED:ACQ_ERROR

Funding transaction was declined and payment not send

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

AML_ERROR

User was found on the stop list

NETWORK_ERROR

Acceptance network is unavailable

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

CURRENCY_NOT_SUPPORTED

Currency is not supported

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

ERROR_SENDER_CARD_IS_BLOCKED

Sender’s card is blocked

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

ERROR_SENDER_USER_IS_BLOCKED

User acting as sender is blocked

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

ERROR_SENDER_BIN_IS_BLOCKED

BIN of sender’s card is blocked

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

ERROR_MONITORING

Some unrecognized error occurred

ERROR_MPI_CONNECTION

Couldn’t established connection to MPI service

FUNDING_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Funding transaction declined - mip response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

FUNDING_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Funding process failed and it is need to manual verification of transaction

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

FUNDING_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Funding transaction declined - mip_proxy response timeout

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

ERROR_3DS_2_X_CARD_FLOW_INVOKED_FOR_OTHER_CARD_NUMBER_THAN_SPECIFIED_IN_THE_REQUEST

TransactionXId is invalid for card number specified in the request, 3DS 2.X flow invoked for other card number than specified in the request

ERROR_3DS_2_X_CARD_FLOW_INVOKED_FOR_OTHER_MERCHANT_THAN_SPECIFIED_IN_THE_REQUEST

TransactionXId is invalid for merchant specified in the request, 3DS 2.X flow invoked for other merchant than specified in the request

ERROR_3DS_2_X_NOT_FOUND_CARD_AUTHENTICATION_BY_TRANSACTION_XID

Card not found by transactionXId

ERROR_3DS_2_X_CARD_AUTHENTICATION_DOES_NOT_MATCH_TO_PAYMENT_TYPE

Card authentication does not match to payment type

ERROR_3DS_2_X_FAILED

Error 3DS 2.X processing failed

ERROR_3DS_2_X_REQUIRED_DATA_NOT_COMPLETE

Required configuration data of Merchant are not complete to finish 3DS 2.X process

ERROR_MPI2_INTERNAL_ERROR

Some unrecognized, internal error occurred in MPI2 service

ERROR_3DS_VERSION_NOT_ENROLLED

Merchant has configured a different version of 3DS than specified in the request

ERROR_NO_3DS_AUTHORIZATION

Error no 3ds authorization, when User authenticates successfully but after 15 minutes or User doesn’t authenticate.

ERROR_MPI_STATUS_TO_LOW: Initialize/Finalize: U/N

Error occurs, when merchant configuration allows only for attempted or full authenticated 3DS transactions with mpi status 'A' or 'Y' but mpi service has returned other status e.g. 'N' or 'U' at any stage of the transaction.

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

ERROR_CARD_NOT_FOUND

Card was not found

ERROR_VALIDATION

Some validation error occurred

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

LIMIT_ERROR

Error during limit checking

MASTERCARD_MAC_TPE_EXCELLENCE_RULE

Transaction rejected, second transaction with merchant advice code 03 or 21 within 30 days.

ERROR_SOMETHING_WRONG

An unrecognized error occurred

AMOUNT_IS_TOO_SMALL

The amount sent is too small. Enter a larger amount

AMOUNT_IS_TOO_HIGH

The amount sent is too high. Enter a lower amount

500 Internal Server Error - Card Blocked
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1
{
    "status" : "ERROR_RECEIVER_CARD_IS_BLOCKED"
    "cardBlockData": {
        "blockType": "TEMP",
        "blockedUntil": "2022-09-24T14:03:56.000"
    }
}

After receiving these statuses, the transaction was rejected

Error statuses

Name Description Allow to try again

WAITING_FOR_RECEIVER_TIMEOUT

The time of 12 hours has been exceeded

No

ERROR_DELAYED_PAYMENT_ATTEMPTS_EXCEEDED

The number of 3 payment attempts has been exceeded

No

ERROR_DELAYED_PAYMENT_TRX_NOT_REGISTERED_FOR_DELAYED_PROCESSING

Payment of transaction was not registered for delayed processing. Cannot process payment

No

ERROR_DELAYED_PAYMENT_NOT_FOUND

There is no Delayed Payment with given orderId

No

ERROR_DELAYED_PAYMENT_UNEXPECTED_EXCEPTION_OCCURRED

Critical internal exception occurred in system while trying to make Delayed Payment

Yes

ERROR_DELAYED_PAYMENT_RECEIVER_NOT_PRESENT

There is no receiver with given phone or email.

Yes

PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

Yes

ISSUER_NOT_SUPPORTED

This card is not supported

Yes

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

Yes

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

Yes

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

Yes

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

Yes

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

Yes

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

Yes

AML_ERROR

User was found on the stop list

Yes

NETWORK_ERROR

Acceptance network is unavailable

Yes

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

Yes

CURRENCY_NOT_SUPPORTED

Currency is not supported

Yes

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

Yes

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

Yes

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

Yes

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

Yes

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

Yes

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

Yes

ERROR_MONITORING_UNAUTHORIZED

Error with service authorization occurred

Yes

ERROR_MONITORING

Some unrecognized error occurred

Yes

ERROR_USER_NOTFOUND

Some problem with authorized the user.

Yes

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

No

ERROR_MPI_CONNECTION

Couldn’t established connection to MPI service

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

Yes

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

Yes

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

Yes

ERROR_CARD_NOT_FOUND

Card was not found

No

ERROR_DATACORE_CONNECTION

Problem with DC

Yes

ERROR_VALIDATION

Some validation error occurred

Yes

ERROR_SOMETHING_WRONG

An unrecognized error occurred

Yes

ERROR_MERCHANT_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

Merchant is marked as high risk and does not allow the execution of transaction with the given card country

Yes

ERROR_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the given card country

Yes

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

Yes

200 OK - Error validation
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
	"status" : "ERROR_VALIDATION",
	"error" : {
		"message": "Some information is missing or incorrect.",
		"errors": [{
				"field": "requestId",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "cvc2",
				"message": [
					"may not be null",
					"length must be 3"
				]
			},
			{
				"field": "type",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "amount",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "sender.cardNumber",
				"message": [
					"may not be null",
					"may not be empty",
					"card number length must be 16"
				]
			},
			{
				"field": "sender.expirationDate",
				"message": [
					"invalid card expiration date",
					"may not be null",
					"may not be empty"
				]
			},
			{
				"field": "sender.city",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 25"
				]
			},
			{
				"field": "sender.street",
				"message": [
					"may not be null",
					"may not be empty",
					"length must be between 1 and 50"
				]
			},
            {
				"field": "sender.postalCode",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10"
				]
			},
            {
                "field": "sender.flatNumber",
                "message": [
                    "must be null",
                    "length must be between 0 and 5"
                ]
            },
			{
				"field": "sender.lastName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
			{
				"field": "sender.houseNumber",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 1 and 10",
                    "must match the expression: ^[1-9][0-9]{0,4}(?:[A-z]?[0-9]{0,4})?((?:[-/ ][1-9]?[A-z]?[0-9]{0,4})*[A-z]?)?$"
				]
			},
			{
				"field": "sender.firstName",
				"message": [
					"may not be empty",
					"may not be null",
					"length must be between 2 and 35"
				]
			},
            {
				"field": "sender.email",
				"message": [
					"may not be empty",
					"may not be null",
					"not a well-formed email address",
					"lenght must be beetween 1 and 128"
				]
			},
			{
				"field": "receiver",
				"message": [
					"may not be null"
				]
			},

			{
				"field": "receiver.currency",
				"message": [
					"may not be null"
				]
			},
			{
				"field": "receiver.phoneNumber",
				"message": [
					"may not be null",
					"may not be empty"
				]
			},
            {
				"field": "receiver.email",
				"message": [
					"may not be null",
					"may not be empty"
				]
			},
            {
                "field": "receiver",
                "message": [
                    "Phone number or email must be present"
                ]
            },
			{
                "field": "sender",
                "message": [
                     "province is mandatory only if country code is US or CA"
                ]
            },
            {
                "field": "sender.province",
                "message": [
                      "is not correct province code for country code US",
                      "may not be null"
                ]
            },
            {
                "field": "sender.province",
                 "message": [
                       "may not be null",
                       "is not correct province code for country code CA"
                 ]
            },
            {
                 "field": "sender.province",
                 "message": [
                        "must match ^[A-Z]{2}$",
                        "is not correct province code for country code US"
                 ]
            },
            {
                 "field": "sender.currency",
                 "message": [
                       "Currency is not supported"
                ]
            },
            {
                 "field": "receiver.currency",
                 "message": [
                       "Currency is not supported"
                ]
            }
		]
	}
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_API_TOKEN_NOT_FOUND",
    "error": {
        "message": "API-TOKEN header not found in request with DATACORE/PHONE model in sender or receiver."
    }
}
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
    "status": "ERROR_MERCHANT_NOT_SUPPORT_CARD_PROVIDER",
    "error": {
        "message": "Merchant not support the given card provider, please check merchant configuration"
    }
}
Errors mentioned below may occur if card’s country is other than user’s country for USA or CAN transaction
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE_FOR_PLAIN",
    "error": {
        "message": "Card country code not compatible with user country code. Please update country in request."
    }
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_WHILE_VALIDATING_CARD_COUNTRY_CODE_AND_USER_COUNTRY_CODE",
    "error": {
        "message": "Card country code not compatible with user country code. Please update user profile."
    }
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_WHILE_GETTING_COUNTRY_CODE",
    "error": {
        "message": "Could not get card country code"
    }
}
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_WHILE_VALIDATING_PROVINCE_NOT_CORRECT_PROVINCE_CODE",
    "error": {
        "message": "Province code is not valid province code. Please update user profile"
    }
}
Error described bellow may occur when merchant tries to make transaction in other model than assigned primarily. For example, if merchant’s model is set as Card-Card and then merchant will try to make transaction in Cash-Card model, will receive error as bellow.
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "sender.type",
                "message": [
                    "Sender type violates merchant model"
                ]
            }
        ]
    }
}
Errors below may occur when a merchant uses a sender card or a receiver card issued in a country that is on the list of countries High Risk excluded from the Fenige API transactions. The transaction is treated as high risk and rejected. Please contact support.
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
    "status": "ERROR_MERCHANT_FUNDING_CARD_COUNTRY_RESTRICTED",
    "error": {
        "message": "Restricted funding card country was used."
    }
}
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
    "status": "ERROR_MERCHANT_PAYMENT_CARD_COUNTRY_RESTRICTED",
    "error": {
        "message": "Restricted payment card country was used."
    }
}
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
    "status": "ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED",
    "error": {
        "message": "Geographic scope is not permitted for this transaction"
    }
}
Errors below may occur when a merchant uses a sender card or a receiver card issued in a country that is on the list of countries excluded from the Fenige API transactions. Please contact support.
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
"status": "ERROR_FUNDING_CARD_COUNTRY_RESTRICTED",
"error": {
"message": "Restricted funding card country was used."
}
}
HTTP/1.1 200 OK
Content-Type: application/json;charset=ISO-8859-1

{
"status": "ERROR_PAYMENT_CARD_COUNTRY_RESTRICTED",
"error": {
"message": "Restricted payment card country was used."
}
}
Errors mentioned below may occur if sender firstName and lastName are the same
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "sender.firstName",
                "message": [
                    "invalid sender firstName and lastName the same"
                ]
            }
        ]
    }
}
Errors mentioned below may occur if sender firstName or lastName contains all the same characters
HTTP/1.1 200 OK
Content-Type: application/json

{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "sender.firstName",
                "message": [
                    "invalid sender firstName contains all the same characters"
                ]
            }
        ]
    }
}
{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "sender.lastName",
                "message": [
                    "invalid sender lastName contains all the same characters"
                ]
            }
        ]
    }
}
401 UNAUTHORIZED
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "Username or password is not correct",
      "path": "/client/delayed/send-money"
}
HTTP/1.1 401 Unauthorized
Content-Type: application/json

{
      "timestamp": "2021-12-22T12:39:53.168+0000",
      "status": 401,
      "error": "Unauthorized",
      "message": "ERROR_USER_NOTFOUND",
      "path": "/client/delayed/send-money"
}
Table 26. Response fields
Path Description

timestamp

Time when request was executed

status

Http response code

error

Http status name

message

Message for response code

path

Path to a specific resource

403 FORBIDDEN
HTTP Response - Error
HTTP/1.1 403 Forbidden
Content-Type: application/json

{
    "timestamp": 1610464313387,
    "status": 403,
    "error": "Forbidden",
    "message": "No message available",
    "path": "/client/delayed/send-money"
}

3.5.2. Delayed Payment

POST /client/delayed/payment Content-Type: application/json, Authorization: Basic Auth, API-TOKEN*
The Delayed Payment method is used to send the Receiver's data and finalize the transaction flow. In order to make this Payment, user must do Funding firstly.
In response to Funding, we get an 'orderId' field, which we must use in the Delayed Payment request's body.
If the Funding has not been completed or if the Funding has already been completed (with success or with failure), Payment will not be processed.
Since october '22 it is possible to make delayed payment with cardId so we don't need to know plain card number now and we can user data stored before. Look at MASTERCARD
(cardId) and VISA(cardId) tabs.
The maximum time for the execution of Delayed Payment after earlier calling Delayed Send Money is 12 hours. After 12 hours after Funding without Payment, it will be reversed and sender will get their funds back. Your server will receive Webhook Event after Reversal Funding if webhook is enabled in your merchant configuration.
There is 3 attempts to execute Delayed Payment after earlier call Delayed Send Money.
Delayed Payment Examples
DELAYED_PAYMENT_REMEMBER_RECEIVER
DP PAYMENT DELAYED RECEIVER REMEMBER
DELAYED_PAYMENT_NOT_REMEMBER_RECEIVER
DP PAYMENT DELAYED RECEIVER NOT REMEMBER
Example HTTP Request
VISA(Phone)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 338
Host: java-staging.fenige.pl:8181

{
  "orderId" : "215f7ae3-512a-47c1-8abe-ef66f3acf895",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "cardNumber" : "4485909148265810",
    "rememberReceiver" : false,
    "phoneNumber" : "48560740349",
    "currency" : "PLN"
  },
  "requestId" : "215f7ae3-512a-47c1-8abe-ef66f3acf895"
}
Table 27. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be "DELAYED".

receiver.firstName

String

Required

@NotNull

Receiver first name.

receiver.lastName

String

Required

@NotNull

Receiver last name.

receiver.cardNumber

String

Required

@NotNull

Receiver card number.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.phoneNumber

String

Required

@NotNull

Receiver phone number.

receiver.rememberReceiver

Boolean

Required

@NotNull

By sending this field as 'true' value you can save receiver.

MASTERCARD(Phone)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 338
Host: java-staging.fenige.pl:8181

{
  "orderId" : "8f1527bb-78a5-4a09-b1cd-6f07f300daa7",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "cardNumber" : "5117964247989169",
    "rememberReceiver" : false,
    "phoneNumber" : "48560740349",
    "currency" : "PLN"
  },
  "requestId" : "8f1527bb-78a5-4a09-b1cd-6f07f300daa7"
}
Table 28. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be "DELAYED".

receiver.firstName

String

Required

@NotNull

Receiver first name.

receiver.lastName

String

Required

@NotNull

Receiver last name.

receiver.cardNumber

String

Required

@NotNull

Receiver card number.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.phoneNumber

String

Required

@NotNull

Receiver phone number.

receiver.rememberReceiver

Boolean

Required

@NotNull

By sending this field as 'true' value you can save receiver.

VISA(Email)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 340
Host: java-staging.fenige.pl:8181

{
  "orderId" : "5f436fc6-c6b4-4465-88bc-fc1d4ce916ad",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "rob.wring@fenige.pl",
    "cardNumber" : "4485909148265810",
    "rememberReceiver" : false,
    "currency" : "PLN"
  },
  "requestId" : "5f436fc6-c6b4-4465-88bc-fc1d4ce916ad"
}
Table 29. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be "DELAYED".

receiver.firstName

String

Required

@NotNull

Receiver first name.

receiver.lastName

String

Required

@NotNull

Receiver last name.

receiver.email

String

Required

@NotNull

Receiver email.

receiver.cardNumber

String

Required

@NotNull

Receiver card number.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.rememberReceiver

Boolean

Required

@NotNull

By sending this field as 'true' value you can save receiver.

MASTERCARD(Email)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 340
Host: java-staging.fenige.pl:8181

{
  "orderId" : "cf252d14-d8bf-45df-8725-6655857e94f9",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "rob.wring@fenige.pl",
    "cardNumber" : "5117964247989169",
    "rememberReceiver" : false,
    "currency" : "PLN"
  },
  "requestId" : "cf252d14-d8bf-45df-8725-6655857e94f9"
}
Table 30. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be "DELAYED".

receiver.firstName

String

Required

@NotNull

Receiver first name.

receiver.lastName

String

Required

@NotNull

Receiver last name.

receiver.email

String

Required

@NotNull

Receiver email.

receiver.cardNumber

String

Required

@NotNull

Receiver card number.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.rememberReceiver

Boolean

Required

@NotNull

By sending this field as 'true' value you can save receiver.

VISA(cardId)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 322
Host: java-staging.fenige.pl:8181

{
  "orderId" : "9d38aa06-337c-4643-b590-a7a4fe28be7b",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "rob.wring@fenige.pl",
    "cardId" : 1234,
    "rememberReceiver" : false,
    "currency" : "PLN"
  },
  "requestId" : "9d38aa06-337c-4643-b590-a7a4fe28be7b"
}
Table 31. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be DELAYED.

receiver.email

String

Required

@NotNull

Receiver email.

receiver.cardId

Number

Required

@NotNull

Receiver card id.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.firstName

String

Optional

@NotNull

Receiver first name.

receiver.lastName

String

Optional

@NotNull

Receiver last name.

MASTERCARD(cardId)
POST /client/delayed/payment HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Content-Length: 322
Host: java-staging.fenige.pl:8181

{
  "orderId" : "ae3fee87-e8fb-4702-a31b-dc1ec67b8454",
  "receiver" : {
    "type" : "DELAYED",
    "firstName" : "Rob",
    "lastName" : "Wring",
    "email" : "rob.wring@fenige.pl",
    "cardId" : 1234,
    "rememberReceiver" : false,
    "currency" : "PLN"
  },
  "requestId" : "ae3fee87-e8fb-4702-a31b-dc1ec67b8454"
}
Table 32. Delayed Payment Request Fields
Path Type Validation Rule Description

orderId

String

Required

@NotNull

Unique transaction identifier.

requestId

String

Optional

@Uuid

128 bit number generated by the user, used to identify single transaction. Ensures that the transaction with the given parameter is processed only once.

receiver.type

String

Required

@NotNull

For this configuration the value of this field must be DELAYED.

receiver.email

String

Required

@NotNull

Receiver email.

receiver.cardId

Number

Required

@NotNull

Receiver card id.

receiver.currency

String

Required

@NotNull

Currency for transaction. Example: PLN.

receiver.firstName

String

Optional

@NotNull

Receiver first name.

receiver.lastName

String

Optional

@NotNull

Receiver last name.

Response
Response status

Status

Description

200 OK

Delayed Send Money approved for processing and transaction details returned.

400 Bad Request

Returned when request is incorrect, required fields are missing or the values are not valid.

500 Internal Server Error

Returned when user provides wrong order-id or transaction was failed or was Declined.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1069

{
  "amount" : 2000,
  "amountInUsDollar" : 537,
  "bigDecimalAmount" : 20.0,
  "commission" : 0,
  "bigDecimalCommission" : 0,
  "orderId" : "56359e08-200b-46ae-9bb8-eb0ec5acbced",
  "fundingRrn" : "031420000725",
  "paymentRrn" : "031420000726",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 2000,
    "bigDecimalRevaluationFundingAmount" : 20.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 2000,
    "bigDecimalRevaluationPaymentAmount" : 20.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "Rob",
    "lastName" : "Wring",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Mark",
    "lastName" : "Smith",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "APPROVED",
  "responseCode" : "CODE_00"
}

Response fields

Path Type Description

orderId

String

Unique transaction identifier.

transactionStatus

String

Transaction status.

responseCode

String

Response code.

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult.revaluationFundingAmount

Number

Amount (in pennies) of funding transaction in fundingCurrency.

revaluationResult.bigDecimalRevaluationFundingAmount

Number

Amount of funding transaction in fundingCurrency.

revaluationResult.fundingCurrency

String

Currency code the same as sender’s card currency

revaluationResult.revaluationPaymentAmount

Number

Amount (in pennies) of payment transaction in paymentCurrency.

revaluationResult.bigDecimalRevaluationPaymentAmount

Number

Amount of payment transaction in paymentCurrency.

revaluationResult.paymentCurrency

String

Currency code the same as receiver’s card currency.

revaluationResult.determineCurrencyRate.from

String

Currency which was conversion from.

revaluationResult.determineCurrencyRate.to

String

Resulted currency.

revaluationResult.determineCurrencyRate.currencyRate

String

Currency rate.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

400 Bad request
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json;charset=ISO-8859-1
Content-Length: 104

{
  "error" : {
    "status" : "ERROR_INVALID_JSON",
    "message" : "Some properties are invalid"
  }
}
Errors mentioned below may occur if receiver firstName and lastName are the same
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json
{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "receiver.firstName",
                "message": [
                    "invalid receiver firstName and lastName the same"
                ]
            }
        ]
    }
}
Errors mentioned below may occur if receiver firstName or lastName contains all the same characters
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json
{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "receiver.firstName",
                "message": [
                    "invalid receiver firstName contains all the same characters"
                ]
            }
        ]
    }
}
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json
{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "receiver.lastName",
                "message": [
                    "invalid receiver lastName contains all the same characters"
                ]
            }
        ]
    }
}
Errors mentioned below may occur if sender email is equal to receiver email, but firstName and lastName data are different
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json
{
    "status": "ERROR_VALIDATION",
    "error": {
        "message": "Some information is missing or incorrect.",
        "errors": [
            {
                "field": "sender.email",
                "message": [
                    "invalid sender and receiver email the same for different person"
                ]
            }
        ]
    }
}
500 Internal Server Error
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1
{
"status" : "PAYMENT_TRANSACTION_DECLINED:CODE_05"
}

After receiving these statuses, the transaction was rejected

Error statuses

Name Description Allow to try again

WAITING_FOR_RECEIVER_TIMEOUT

The time of 12 hours has been exceeded

No

ERROR_DELAYED_PAYMENT_ATTEMPTS_EXCEEDED

The number of 3 payment attempts has been exceeded

No

ERROR_DELAYED_PAYMENT_TRX_NOT_REGISTERED_FOR_DELAYED_PROCESSING

Payment of transaction was not registered for delayed processing. Cannot process payment

No

ERROR_DELAYED_PAYMENT_NOT_FOUND

There is no Delayed Payment with given orderId

No

ERROR_DELAYED_PAYMENT_UNEXPECTED_EXCEPTION_OCCURRED

Critical internal exception occurred in system while trying to make Delayed Payment

Yes

ERROR_DELAYED_PAYMENT_RECEIVER_NOT_PRESENT

There is no receiver with given phone or email.

Yes

PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

Yes

ISSUER_NOT_SUPPORTED

This card is not supported

Yes

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

Yes

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

Yes

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

Yes

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

Yes

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

Yes

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

Yes

AML_ERROR

User was found on the stop list

Yes

NETWORK_ERROR

Acceptance network is unavailable

Yes

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

Yes

CURRENCY_NOT_SUPPORTED

Currency is not supported

Yes

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

Yes

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

Yes

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

Yes

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

Yes

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

Yes

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

Yes

ERROR_MONITORING

Some unrecognized error occurred

Yes

ERROR_USER_NOTFOUND

Some problem with user authorization in Datacenter

Yes

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

No

ERROR_MPI_CONNECTION

Couldn’t established connection to MPI service

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

Yes

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

Yes

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

Yes

ERROR_CARD_NOT_FOUND

Card was not found

No

ERROR_DATACORE_CONNECTION

Problem with DC

Yes

ERROR_VALIDATION

Some validation error occurred

Yes

ERROR_MERCHANT_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

Merchant is marked as high risk and does not allow the execution of transaction with the given card country

Yes

ERROR_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the given card country

Yes

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

Yes

ERROR_SINGLE_TRANSACTION_LIMIT

Transaction limit for single transaction exceeded

Yes

ERROR_DAILY_TRANSACTION_LIMIT

Daily transaction limit for amount per card exceeded

Yes

ERROR_DAILY_COUNT_TRANSACTION_LIMIT

Daily transaction limit for count per card exceeded

Yes

ERROR_MONTHLY_TRANSACTION_LIMIT

Monthly transaction limit for amount per card exceeded

Yes

ERROR_MONTHLY_COUNT_TRANSACTION_LIMIT

Monthly transaction limit for count per card exceeded

Yes

ERROR_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per card was exceeded

Yes

ERROR_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per card was exceeded

Yes

ERROR_MERCHANT_MASTERCARD_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard cards was exceeded

Yes

ERROR_MERCHANT_MASTERCARD_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard cards was exceeded

Yes

ERROR_MERCHANT_VISA_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using visa cards was exceeded

Yes

ERROR_MERCHANT_VISA_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using visa cards was exceeded

Yes

ERROR_MERCHANT_DAILY_CUMULATIVE_LIMIT

Daily cumulative limit per merchant transactions using mastercard and visa cards was exceeded

Yes

ERROR_MERCHANT_MONTHLY_CUMULATIVE_LIMIT

Monthly cumulative limit per merchant transactions using mastercard and visa cards was exceeded

Yes

LIMIT_ERROR

Error during limit checking

Yes

ERROR_SOMETHING_WRONG

An unrecognized error occurred

Yes

500 Internal Server Error (CARD BLOCKED)
HTTP/1.1 500 Internal Server Error
Content-Type: text/plain;charset=ISO-8859-1
{
    "status" : "ERROR_RECEIVER_CARD_IS_BLOCKED"
    "cardBlockData": {
        "blockType": "TEMP",
        "blockedUntil": "2022-09-24T14:03:56.000"
    }
}

After receiving these statuses, the transaction was rejected

Error statuses

Name Description Allow to try again

WAITING_FOR_RECEIVER_TIMEOUT

The time of 12 hours has been exceeded

No

ERROR_DELAYED_PAYMENT_ATTEMPTS_EXCEEDED

The number of 3 payment attempts has been exceeded

No

ERROR_DELAYED_PAYMENT_TRX_NOT_REGISTERED_FOR_DELAYED_PROCESSING

Payment of transaction was not registered for delayed processing. Cannot process payment

No

ERROR_DELAYED_PAYMENT_NOT_FOUND

There is no Delayed Payment with given orderId

No

ERROR_DELAYED_PAYMENT_UNEXPECTED_EXCEPTION_OCCURRED

Critical internal exception occurred in system while trying to make Delayed Payment

Yes

ERROR_DELAYED_PAYMENT_RECEIVER_NOT_PRESENT

There is no receiver with given phone or email.

Yes

PAYMENT_TRANSACTION_DECLINED:CODE_XX

CODE_XX - is MasterCard response code (ISO 8583)

Yes

ISSUER_NOT_SUPPORTED

This card is not supported

Yes

ERROR_CARD_IS_BLOCKED

Card is blocked for 1 hour in Fenige

Yes

ERROR_USER_IS_BLOCKED

User is blocked in Fenige

Yes

ERROR_BIN_IS_BLOCKED

Bin is blocked for 1 hour in Fenige

Yes

ERROR_PAYMENT_BANK_IS_BLOCKED

Payment bank is blocked in Fenige

Yes

PAYMENT_TRANSACTION_DECLINED:ACQ_ERROR

Payment transaction was declined and funding was reversed

Yes

ERROR_ACQ_CONNECTION

A connection error occurred to Acquirer service

Yes

AML_ERROR

User was found on the stop list

Yes

NETWORK_ERROR

Acceptance network is unavailable

Yes

CURRENCY_RATES_NOT_FOUND

No currently effective rates found in the database

Yes

CURRENCY_NOT_SUPPORTED

Currency is not supported

Yes

MERCHANT_CURRENCY_NOT_SUPPORTED

Currency is not supported by Merchant

Yes

ERROR_RECEIVER_CARD_IS_BLOCKED

Receiver’s card is blocked

Yes

ERROR_RECEIVER_USER_IS_BLOCKED

User acting as receiver is blocked

Yes

ERROR_RECEIVER_BIN_IS_BLOCKED

BIN of receiver’s card is blocked

Yes

ERROR_AMOUNT_IS_BLOCKED

Amount is higher than acceptable limit

Yes

ERROR_MONITORING_CONNECTION

Couldn’t established connection to Monitoring service

Yes

ERROR_MONITORING

Some unrecognized error occurred

Yes

ERROR_USER_NOTFOUND

Some problem with authorized the user.

Yes

ERROR_USER_VERIFICATION

The transaction user’s personal data verified as incorrect on the verification service. Transaction rejected.

No

ERROR_MPI_CONNECTION

Couldn’t established connection to MPI service

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_RESPONSE_TIMEOUT

Payment transaction declined - mip response timeout

Yes

PAYMENT_TRANSACTION_DECLINED:NEED_MANUAL_VERIFICATION

Payment process failed and it is need to manual verification of transaction

Yes

PAYMENT_TRANSACTION_DECLINED:MIP_PROXY_RESPONSE_TIMEOUT

Payment transaction declined - mip_proxy response timeout

Yes

ERROR_TRANSACTION_NOT_FOUND

Error transaction not exists

Yes

ERROR_CARD_NOT_FOUND

Card was not found

No

ERROR_DATACORE_CONNECTION

Problem with DC

Yes

ERROR_VALIDATION

Some validation error occurred

Yes

ERROR_SOMETHING_WRONG

An unrecognized error occurred

Yes

ERROR_MERCHANT_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

Merchant is marked as high risk and does not allow the execution of transaction with the given card country

Yes

ERROR_DELAYED_PAYMENT_CARD_COUNTRY_RESTRICTED

System does not allow the execution of transaction with the given card country

Yes

ERROR_TRANSACTION_GEOGRAPHIC_SCOPE_BLOCKED

Geographic scope is not permitted for this transaction

Yes

3.5.3. Transaction history

GET /client/{clientId}/transactions?page=0&size=100 Content Type: application/json, Authorization: Basic Auth
Method return page with list of user transactions. Transactions are filtered by clientId provided in GET parameter.
User can send additional optional parameters (page, size) to obtain given page with defined size.
Request
GET /client/0/transactions?fromDate=2018-03-06&toDate=2018-03-08&page=0&size=100 HTTP/1.1
Content-Type: application/json
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned list of transactions history.

404 NOT FOUND

Returning the list failed.

Example Response
200 OK - phone receiver
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1073

{
  "content" : [ {
    "correlationId" : "3ff8fe8d-c31f-4546-9fa3-d5d4359de151",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverFirstName" : "Patrick",
    "receiverLastName" : "Evans",
    "receiverHiddenCardNumber" : "511123******1234",
    "receiverProvider" : "MASTERCARD",
    "receiverBankName" : "Bank Polska Kasa Opieki Spółka Akcyjna",
    "receiverPhone" : "600300200",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "OUTGOING",
    "3DS" : true
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system.

content.[].createdDate

String

Date of transaction processing.

content.[].amount

Number

Transaction amount in pennies.

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency.

content.[].currency

String

Transaction currency.

content.[].cardId

Number

Datacore card id used in transaction (sender card).

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].receiverFirstName

String

Transaction receiver first name.

content.[].receiverLastName

String

Transaction receiver last name.

content.[].receiverHiddenCardNumber

String

Transaction receiver hidden card number.

content.[].receiverProvider

String

VISA or MASTERCARD or MAESTRO

content.[].receiverBankName

String

Transaction receiver card bank name.

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card numbe.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverPhone

String

Transaction receiver phone number.

content.[].status

String

Status of the transaction (approved, reversed, rejected).

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false).

totalPages

Number

Total number of all pages.

totalElements

Number

Total number of all transactions.

numberOfElements

Number

Number of transactions on page.

first

Boolean

Describes whether the page is first (true ot false).

sort

Object

Details of sort.

size

Number

Max number of transactions on page.

number

Number

Page number.

pageable

String

Requested page information.

200 OK - email receiver
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1082

{
  "content" : [ {
    "correlationId" : "cd265d59-887c-43e4-90d9-37cc54ad183e",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverFirstName" : "Patrick",
    "receiverLastName" : "Evans",
    "receiverHiddenCardNumber" : "511123******1234",
    "receiverProvider" : "MASTERCARD",
    "receiverBankName" : "Bank Polska Kasa Opieki Spółka Akcyjna",
    "receiverEmail" : "receiver@fenige.pl",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "INCOMING",
    "3DS" : true
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system.

content.[].createdDate

String

Date of transaction processing.

content.[].amount

Number

Transaction amount in pennies.

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency.

content.[].currency

String

Transaction currency.

content.[].cardId

Number

Datacore card id used in transaction (sender card).

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].receiverFirstName

String

Transaction receiver first name.

content.[].receiverLastName

String

Transaction receiver last name.

content.[].receiverHiddenCardNumber

String

Transaction receiver hidden card number.

content.[].receiverProvider

String

VISA or MASTERCARD or MAESTRO

content.[].receiverBankName

String

Transaction receiver card bank name.

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card number.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverEmail

String

Transaction receiver email.

content.[].status

String

Status of the transaction (approved, reversed, rejected).

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false).

totalPages

Number

Total number of all pages.

totalElements

Number

Total number of all transactions.

numberOfElements

Number

Number of transactions on page.

first

Boolean

Describes whether the page is first (true ot false).

sort

Object

Details of sort.

size

Number

Max number of transactions on page.

number

Number

Page number.

pageable

String

Requested page information.

200 OK - phone receiver (funding only)
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 841

{
  "content" : [ {
    "correlationId" : "cc2c1b58-29ea-406e-ad31-33f38a583a7c",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverPhone" : "600300200",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "OUTGOING",
    "3DS" : true
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system.

content.[].createdDate

String

Date of transaction processing.

content.[].amount

Number

Transaction amount in pennies.

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency.

content.[].currency

String

Transaction currency.

content.[].cardId

Number

Datacore card id used in transaction (sender card).

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card number.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverPhone

String

Transaction receiver phone number.

content.[].status

String

Status of the transaction (approved, reversed, rejected).

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false).

totalPages

Number

Total number of all pages.

totalElements

Number

Total number of all transactions.

numberOfElements

Number

Number of transactions on page.

first

Boolean

Describes whether the page is first (true ot false).

sort

Object

Details of sort.

size

Number

Max number of transactions on page.

number

Number

Page number.

pageable

String

Requested page information.

200 OK - email receiver (funding only)
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 850

{
  "content" : [ {
    "correlationId" : "2279ca01-819f-47b5-a77c-b80e305b6481",
    "createdDate" : "2018-03-15T10:24:52.149Z",
    "amount" : 15000,
    "amountInUsDollar" : 4024,
    "textAmount" : "150.00 PLN",
    "currency" : "PLN",
    "cardId" : 3574,
    "receiverEmail" : "receiver@fenige.pl",
    "senderFirstName" : "Rob",
    "senderLastName" : "Wring",
    "senderHiddenCardNumber" : "522212******4321",
    "senderProvider" : "MASTERCARD",
    "senderBankName" : "Alior Bank SA",
    "status" : "approved",
    "transactionDirection" : "OUTGOING",
    "3DS" : true
  } ],
  "pageable" : "INSTANCE",
  "last" : true,
  "totalElements" : 1,
  "totalPages" : 1,
  "first" : true,
  "size" : 1,
  "number" : 0,
  "sort" : {
    "empty" : true,
    "sorted" : false,
    "unsorted" : true
  },
  "numberOfElements" : 1,
  "empty" : false
}

Response fields

Path Type Description

content.[].correlationId

String

Unique UUID describing single transaction in system.

content.[].createdDate

String

Date of transaction processing.

content.[].amount

Number

Transaction amount in pennies.

content.[].amountInUsDollar

Number

Transaction amount in USD currency in pennies.

content.[].textAmount

String

Transaction amount with currency.

content.[].currency

String

Transaction currency.

content.[].cardId

Number

Datacore card id used in transaction (sender card).

content.[].3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

content.[].senderFirstName

String

Transaction sender first name.

content.[].senderLastName

String

Transaction sender last name.

content.[].senderHiddenCardNumber

String

Transaction sender hidden card number.

content.[].senderProvider

String

VISA or MASTERCARD or MAESTRO

content.[].senderBankName

String

Transaction sender card bank name.

content.[].receiverEmail

String

Transaction receiver email.

content.[].status

String

Status of the transaction (approved, reversed, rejected).

content.[].transactionDirection

String

Direction of the transaction (INCOMING, OUTGOING)

content.[].merchantAdviceCode

String

Information about the reasons for declined transactions and actions that merchants can take. Occurs only for mastercard and for rejected transactions if Mastercard returns this information

last

Boolean

Describes whether the page is last (true ot false).

totalPages

Number

Total number of all pages.

totalElements

Number

Total number of all transactions.

numberOfElements

Number

Number of transactions on page.

first

Boolean

Describes whether the page is first (true ot false).

sort

Object

Details of sort.

size

Number

Max number of transactions on page.

number

Number

Page number.

pageable

String

Requested page information.

404 NOT FOUND
HTTP/1.1 404 Not Found

3.5.4. Check detailed status

GET /client/send-money/details/{orderId}, Authentication: Basic Auth
    The method allows obtaining a detailed status of multi-currency transaction specified by order-id. Parameter order-id was returned in the previous step (Send money
multicurrency).

From January 2021, there is an internal functionality to restrict access for the Merchant to specific method. The Fenige employee can disable access to a given endpoint, then the HTTP status 403 FORBIDDEN will be returned. The Merchant will be informed about each access restriction action.

Request
Table 33. /client/send-money/details/{orderId}
Parameter Description

orderId

Unique transaction identifier.

GET /client/send-money/details/00549d98-08cb-45d2-8673-4dcafa81f498 HTTP/1.1
Authorization: Basic bWVyY2hhbnQ6cGFzc3dvcmQ=
Host: java-staging.fenige.pl:8181
Response
Response status
Status Description

200 OK

Returned if the transaction completes successfully.

203 NON-AUTHORITATIVE INFORMATION

Returned when transaction was registered for processing. Check status in a while.

404 NOT FOUND

Returned when a transaction related to the given orderId doesn’t exist.

422 UNPROCESSABLE ENTITY

Returned when user provides wrong order-id or transaction was failed or was Declined.

500 INTERNAL SERVER ERROR

Returned when an internal error occur.

Example HTTP Response
200 OK
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 1159

{
  "transactionId" : "TRX220132AM",
  "amount" : 1000,
  "amountInUsDollar" : 268,
  "bigDecimalAmount" : 10.0,
  "commission" : 200,
  "bigDecimalCommission" : 2.0,
  "orderId" : "00549d98-08cb-45d2-8673-4dcafa81f498",
  "createdDate" : "03-04-2018, 14:01",
  "fundingRrn" : "014011103023",
  "paymentRrn" : "014011103024",
  "arn" : "05411640143500000019325",
  "3DS" : true,
  "revaluationResult" : {
    "revaluationFundingAmount" : 1000,
    "bigDecimalRevaluationFundingAmount" : 10.0,
    "fundingCurrency" : "PLN",
    "revaluationPaymentAmount" : 1000,
    "bigDecimalRevaluationPaymentAmount" : 10.0,
    "paymentCurrency" : "PLN",
    "determineCurrencyRate" : {
      "from" : "PLN",
      "to" : "PLN",
      "currencyRate" : "1"
    }
  },
  "receiver" : {
    "firstName" : "John",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "557455******1623",
    "bankName" : "Alior Bank SA"
  },
  "sender" : {
    "firstName" : "Caroline",
    "lastName" : "Novak",
    "provider" : "MASTERCARD",
    "hiddenCardNumber" : "511796******9169",
    "bankName" : "Alior Bank SA"
  },
  "transactionStatus" : "APPROVED"
}

Response fields

Path Type Description

amount

Number

Field informing about the amount of cash transferred in one hundredth of the currency. [1PLN = 100]

amountInUsDollar

Number

Field informing about the amount of cash transferred in one hundredth of the USD currency. [1USD = 100]

bigDecimalAmount

Number

Field informing about the amount of cash transferred with decimal precision.

commission

Number

This is the amount of commission that has been added to the transaction in hundredths. [1 PLN = 100]

bigDecimalCommission

Number

This is the amount of commission that was added to the transaction at 0.01 currency.

orderId

String

Unique transaction identifier.

transactionId

String

The transactionId field is used for the Merchant to send its own internal transaction identifier. This field is returned in the response from the Check status method and sent by the Webhooks method. @Length(max = 64). Optional

createdDate

String

Date of transaction.

fundingRrn

String

Funding Retrieval Reference Number.

paymentRrn

String

Payment Retrieval Reference Number.

arn

String

Acquirer Reference Number

3DS

Boolean

Value: true/false determines if transaction was processed with 3ds

revaluationResult

Object (RevaluationResult)

Detailed information about revaluation between sender currency and receiver currency.

receiver

Object

Personal data of the person to whom the transfer is addressed.

sender

Object

Personal data of the person who performs the transfer of cash.

transactio