For the complete documentation index, see llms.txt. This page is also available as Markdown.

Actions

Test request (GET /ping)

Name
Description
Example

message

Message

PONG!

date

Current date and time on the server

2016-06-30 14:09:20

Status represents the final result of processing the operation

Status represents the current order state

curl -v -X GET -H 'Content-Type: application/json' 'http://project:***@api.box:5001/ping'

> GET /ping HTTP/1.1
> Authorization: Basic cHJvamVjdDpwYXNzd29yZA==
> Host: api.box:5001
> Content-Type: application/json 
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 48 
<
{
  "date": "2016-08-22 15:39:42",
  "message": "PONG!"
}

Fetching data

When fetching data such as a list of orders, the number of rows in response is limited to 2000 per page. Please use some filters to narrow the search. Follow links in HTTP headers to scroll through pages.

Order information (GET /orders/:id)

Name
Description
Example

expand

MessagList of extra objects to display. Possible expands are: card, client, location, custom_fields, issuer, secure3d, operations.cashflow

card, location, client

Status
Possible operations
Description

amount

9.99

Order amount

amount_charged

9.99

Charged amount

amount_refunded

5.99

Refunded amount

auth_code

AUTH12

Authorization code

card

-

Card details (*)

*.holder

John Smith

Cardholder name

*.subtype

classic

Card subtype

*.type

visa

Card type

client

-

Client details (*)

*.address

Main ave. 1

Street address

*.city

San Francisco

City

*.country

USA

Country

*.email

foo@bar.com

E-mail

*.name

John Smith

Full name

*.phone

+14568901231

Phone number

*.state

CA

State

*.zip

12345

Postal code

*.login

john_doe

Login

created

2014-06-30 14:38:48

Creation date and time

currency

USD

Requested payment currency (ISO-4217 3-alpha code)

description

Book sale #453

Order description

descriptor

EXAMPLE.COM/12345

Terminal Descriptor

id

5673044075769513

Unique order ID

issuer

-

Card issuer details

*.bin

411111

BIN

*.country

RUS

Country (ISO 3166-1 alpha-3)

*.title

Bank

Bank name

location

-

Client location details (*)

*.country

USA

Country (ISO 3166-1 alpha-3)

*.city

San Francisco

City

*.region

California

Region

*.ip

8.8.8.8

IP-address

merchant_order_id

5678

Merchant's order ID

operations

-

Array of the order operations (*). See the description of fields in the List— of operations

pan

411111****1111

Card number (PAN)

secure3d

-

3-D Secure details (*)

*.reason

force

The reason why 3-D Secure was enabled

*.scenario

full

3-D Secure scenario used

*.authorization_status

Y

Status of authorization

segment

987654321

Segment

status

authorized

Order Status

updated

2014-06-30 14:38:48

Date and time of the last operation

List of orders (GET /orders/)

Name
Description
Example

expand

List of extra objects to display. Possible expands are: card, client, location, custom_fields, issuer, secure3d, operations.cashflow

card,location,client

status

Filter by status

charged,refunded

created_from

Filter by date of creation

2016-01-01 00:00:00

created_to

Filter by date of creation

AUTH12016-01-31 23:59:59

merchant_order_id

Filter by merchant order ID

12345,123456

card.type

Filter by card type

visa,mastercard

card.subtype

Filter by card subtype

electron,maestro

location.ip

Filter by IP address

8.8.8.8,8.8.8.9

client.name

Find by client name or part of it

Smith

client.email

Find by email or part of it

@yahoo.com

issuer.country

Filter by issuer country (ISO 3166-1 alpha-3)

USA

issuer.bin

Filter by issuer BIN

555555,411111

issuer.title

Find by issuer name or part of it

Credit Union

All the fields are the same as described in the Order information.

curl -v -X GET -H 'Content-Type: application/json' 'http://project:***@api.box:5001/orders/'

> GET /orders/ HTTP/1.1
> Authorization: Basic cHJvamVjdDpwYXNzd29yZA==
> Host: api.box:5001
> Content-Type: application/json 
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 5550 
<
{
  "orders": [
    {
      "amount": "9.99",
      "amount_charged": "0.00",
      "amount_refunded": "0.00",
      "auth_code": "AUTH12",
      "created": "2016-08-22 15:39:49",
      "currency": "USD",
      "description": "Book sale #453",
      "descriptor": "TESTMERCH/TERM",
      "id": "23014806815093624",
      "merchant_order_id": "5678",
      "pan": "411111****1111",
      "segment": "987654321",
      "status": "authorized",
      "updated": "2016-08-22 15:39:49"
    },
    {
      "amount": "9.99",
      "amount_charged": "0.00",
      "amount_refunded": "0.00",
      "auth_code": "AUTH12",
      "created": "2016-08-22 15:39:48",
      "currency": "USD",
      "description": null,
      "descriptor": "TESTMERCH/TERM",
      "id": "23014806643308174",
      "merchant_order_id": null,
      "pan": "411111****1111",
      "status": "authorized",
      "updated": "2016-08-22 15:39:48"
    }
  ]
}

List of operations (GET /operations/)

Name
Description
Example

expand

List of extra objects to display. Possible expand is cashflow, extra

cashflow

status

Filter by status

error

type

Filter by type

charge,refund

created_from

Filter by date of creation

2016-01-01 00:00:00

created_to

Filter by date of creation

2016-01-31 23:59:59

Name
Description
Example

amount

Operation amount

9.99

auth_code

Authorization code

AUTH12

created

Operation date and time

2014-06-30 14:38:48

currency

Requested payment currency (ISO-4217 3-alpha code)

USD

iso_message

Response message

Approved

iso_response_code

Response ISO-code

00

status

Operation status

success

type

Operation type

authorize

trace_id

Trace ID

MCC8454300719

cashflow

Financial details (*)

-

*.currency

Accounting currency (ISO-4217 3-alpha code)

EUR

*.amount

Accounting amount

9.00

*.fee

Fee amount

0.00

*.incoming

Income amount

6.00

*.receivable

Receivable amount

5.00

*.reserve

Reserved amount

0.00

Export of currency rates (GET /exchange_rates/)

Name
Description
Example

expand

List of extra objects to display. Possible expand is cashflow, extra

cashflow

status

Filter by status

error

type

Filter by type

charge,refund

created_from

Filter by date of creation

2016-01-01 00:00:00

created_to

Filter by date of creation

2016-01-31 23:59:59

Name
Description
Example

amount

Operation amount

9.99

auth_code

Authorization code

AUTH12

created

Operation date and time

2014-06-30 14:38:48

currency

Requested payment currency (ISO-4217 3-alpha code)

USD

iso_message

Response message

Approved

iso_response_code

Response ISO-code

00

status

Operation status

success

type

Operation type

authorize

trace_id

Trace ID

MCC8454300719

cashflow

Financial details (*)

-

*.currency

Accounting currency (ISO-4217 3-alpha code)

EUR

*.amount

Accounting amount

9.00

*.fee

Fee amount

0.00

*.incoming

Income amount

6.00

*.receivable

Receivable amount

5.00

*.reserve

Reserved amount

0.00

Working with orders

Order creation (POST /orders/create)

Name
Description
Description

amount

Order amount

9.99

Name
Description
Example

currency

Order currency

USD

merchant_order_id

Merchant's order ID

5678

segment

Segment

987654321

description

Order description

Book sale #453

client

Client details (*)

-

*.address

Street address

Main ave. 1

*.city

City

San Francisco

*.country

Country (ISO 3166-1 alpha-3)

USA

*.email

E-mail

foo@bar.com

*.name

Full name

John Smith

*.phone

Phone number

+1 456 890

*.state

State

CA

*.zip

Postal code

123456

*.login

Login

john_doe

custom_fields

Additional custom fields (*), up to 10 additional values

-

location

Client location details (*)

-

*.ip

IP-address

8.8.8.8

options

Options (*)

-

*.expiration_timeout

Session expiration timeout

30m

*.force3d

Forced 3-D Secure verification

1

*.auto_charge

Executes Charge operation (is used for 1-stage payments)

1

*.language

Payment page language

en

*.return_url

URL to redirect customer when the payment is completed

*.template

Payment page layout

12

*.mobile

Mobile layout

1

*.terminal

Terminal

TERM12

*.apple_pay_enabled

Apple Pay support on checkout page

1

*.google_pay_enabled

Google Pay™ support on checkout page

1

*.secure3d20_return_url

Notification URL 3-D Secure 2.0

*.exemption_mit

Exemption MIT flag

1

*.static_link

Static link flag

1

Fields in response are the same as described in Order information.

HTTP-header Location contents a URL of a payment page. Please redirect the cardholder to this URL.

To manage the inclusion of Google Pay™ and Apple Pay on the checkout page using flags *_pay_enabled must be disabled global support in the

settings.

Creating a static link must be enabled in the settings.

Authorize (POST /orders/authorize)

Name
Description
Example

amount

Order amount

9.99

pan

Card number (PAN)

4111111111111111

card

Card details (*)

-

*.cvv

CVV-code (can be configured as optional in project settings)

123

*.holder

Cardholder name (can be configured as optional in project settings,

from 2 to 40 characters)

John Smith

*.expiration_month

Month of the card expiration date

06

*.expiration_year

Year of the card expiration date

2024

location

Client location details (*)

-

*.ip

IP-address

8.8.8.8

Name
Description
Example

currency

Order currency

USD

merchant_order_id

Merchant's order ID

5678

segment

Segment

987654321

description

Order description

Book sale #453

client

Client details (*)

-

*.address

Street address

Main ave. 1

*.city

City

Main ave. 1

*.country

Country (ISO 3166-1 alpha-3)

USA

*.login

Client login

john_doe

*.email

E-mail

foo@bar.com

*.name

Full name

John Smith

*.phone

Phone number

+1 456 890

*.state

State

CA

*.zip

Postal code

123456

*.login

Login

john_doe

custom_fields

Additional custom fields (*)

-

options

Options (*)

-

*.force3d

Forced 3-D Secure verification

1

*.return_url

URL to redirect customer when the payment is completed

http://my.url

*.auto_charge

Executes Charge operation (is used for 1-stage payments)

1

*.terminal

Terminal

TERM12

*.recurring

Flag of the recurring payment

1

*.secure3d20_return_url

Notification URL 3-D Secure 2.0

*.exemption_mit

Exemption MIT flag

1

secure3d

3-D Secure authentication (*)

-

*.xid

PaRes transaction identifier (XID)

8Rg2xYbxLUGsfZlkoh1JxAQ

FBM=

*.cavv

Cardholder authentication verification value from PaRes

AAABCBVRA2EYZXQBV1EDAAA

AAA=

*.eci

E-commerce indicator (ECI)

05

*.ds_trans_id

Directory server transaction ID

Rcm70YAaT/7SZnqVGFQkm/N

JnbQ=

recurring_details

Recurrent payment details (*)

-

*.parent_order_id

Parent order ID

74615664219665657

*.trace_id

Trace ID

MCC8454300719

*.indicator

Recurrent payment indicator

m101

Fields in response are the same as described in Order information and may contain extra fields described below.

Name
Description
Example

form3d_html

3-D Secure form in HTML

<form id="form3d" ...

form3d

3-D Secure form (*)

-

*.MD

MD parameter

NTY3NDg0NjMzMjA0MDU1OQ==

*.PaReq

PaReq parameter

Y3NDg0NjMzM0MDU1OQ

*.TermUrl

System URL where transaction is finalized

*.action

Acquirer ACS URL

*.method

Form method

POST

Examples

Once the authorization request is completed, it has to be followed with Charge operation. It also can be can be done with auto_charge option passed in request or automatically depending on project settings.

If charge is never processed, authorization will be released by the card issuer after some time and authorized amount will be available back to the cardholder.

Reverse (PUT /orders/:id/reverse)

Not supported.

Fields in response are the same as described in Order information.

Charge (PUT /orders/:id/charge)

Name
Description
Example

amount

Amount of charge

9.99

Fields in response are the same as described in Order information.

Refund (PUT /orders/:id/refund)

Name
Description
Example

amount

Amount of refund

9.99

Fields in response are the same as described in Order information.

Cancel (PUT /orders/:id/cancel)

This is the equivalent of making Reverse or Refund depending on current order state.

Name
Description
Example

amount

Amount of refund (not applicable for reversing)

9.99

Fields in response are the same as described in Order information.

Repeating payment (POST /orders/:id/rebill)

Name
Description
Example

amount

Amount

9.99

cvv

CVV-code (can be configured as optional in project settings)

123

location

Client location details (*)

-

*.ip

IP-address

8.8.8.8

Name
Description
Example

options

Options (*)

-

*.recurring

Flag of the recurring payment

1

recurring_details

Recurrent payment details (*)

-

*.trace_id

Trace ID

MCC8454300719

*.indicator

Recurrent payment indicator

m101

Fields in response are the same as described in Order information.

Original credit transaction (OCT) (POST /orders/:id/credit)

Name
Description
Example

amount

Amount

9.99

Optional parameters are the same as for Authorize operation.

Fields in response are the same as described in Order information

Original credit transaction without link to order (OCT) (POST /orders/credit)

Name
Description
Example

amount

Amount

9.99

pan

Card number (PAN)

4111111111111111

Optional parameters are the same as for Authorize operation.

Fields in response are the same as described in Order information.

Authorization with the transfer of an encrypted token ( POST /orders/token_pay)

amount

Amount

9.99

dsrp

DSRP data (*)

-

*.type

Token type

apple_pay

*.token

DSRP token

eyJwYXltZW50RGF0YS...kljcEJhOTR

WTi9KVGdhOFc3NUlXQUE9PSJ9fQ==

location

Client location details (*)

-

*.ip

IP-address

8.8.8.8

Endpoint is transfered encrypted token of Google Pay or Apple Pay. Allowed field values type: google_pay, apple_pay. Optional parameters are the

same as for Authorize, except fields pan, card.*, secure3d.*, options.force3d, options.return_url, options.secure3d20_return_url.

Completion of 3-D Secure Authentication (POST /orders/:id/complete)

Name
Description
Example

PaRes

Payer authentication response

424EF64895CAE9797497F

The endpoint sends a response to the authorization request. When resubmitting the request to the endpoint the answer will be received: "Order already

completed".

Completion of 3-D Secure 2.0 Authentication (POST /orders/:id/complete3d20)

Name
Description
Example

cres

Base64 encoded string containing the results of 3-D

Secure authentication

ewogICJhY3NUcmFuc0...W9uIiA6ICIyLjEuMCIKfQ==

Fields in response are the same as described in Order information.

The endpoint completes authorization performed with 3-D Secure 2.0 authentication. If there is no data in the order properties identification from RReq, a

validation error will be received and order will remain in the prepare status.

Continue 3DS Method URL of authentication (POST /orders/:id/resume)

Not supported

Fields in response are the same as described in Order information

The endpoint continues the authorization described in Payments with 3-D Secure 2.0. Maximum time waiting for a response to a request - 10 seconds

Last updated