Payout Details

Go to Payouts tab from the dashboard and use the search filters to find a specific payout. After you have found the transaction you have been looking for, using the search filters, just double click on it to see specific details of that payout.

A new window will open containing the general details for that Payout ID and also providing details about specific sections, like: General information, Credit Card, Reporting, Flags and Return Codes.

The dashboard Payout Details allows the user to always find specific information in order to be informed and keep track of his day-to-day operations and payouts.

General provides detailed information for the following fields: ID of the transaction, Merchant Transaction ID, Input Date Time, Merchant ID, Merchant Site ID, Method ID, Merchant Alias, Merchant Site Alias, Method Name, Amount, Currency, Status, Statement Descriptor, Originator Transaction ID, Country, Specific Details, Method Transaction ID.

32

Credit Card provides detailed information for the following fields: Masked Card Number, Card Expiration Month, Card Expiration Year, Card Holder Name, Credit Card Brand, Credit Card Sub-Brand.

32

Reporting provides detailed information for the following fields: Notification Date Time, Last Notified Status.

32

Flags provides detailed information for the following fields: Request Version.

32

Return Codes provides detailed information for the following fields: Return Code, Return Code Description.

32

Payouts List

In order to see and verify your payouts go to Payouts tab. Here you will find a complete list of all of your payouts. You have the possibility to search for a specific payout using different criteria, to see the details, and to export your payouts into an Excel file.

32

Search filters

When you access the Payouts tab, the Search Filters section is expanded. In order to collapse it just click the arrow on the right of the screen.

You can search payouts by ID (the payment id in the GlobalPay system), Merchant Transaction ID (the payout id in your system), Method Transaction ID (used for transaction tracking and matching with customer receipt or bank statement), Method, Amount, Currency, Country, Status, Interval (from – to) and Site Alias.

32

Payouts Details

After you have found the transaction you’ve been looking for, using the search filters, just click on it to see the specific details of that payout.

A new window will open containing the general details for that Payout ID and also providing details about specific sections, like: General information, Credit Card, Reporting, Flags, Return Codes.

66

UPI Test Data

For UPI payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

UPI Payment Flow

    1. The customer enters his Email Address, Name and Permanent account number (PAN). Please note that for India the CustomerSocialSecurityNumber parameter consists of PAN. For more information about the PAN please click here.

      1 Enter customer details

    2. The customer logs in to his account by entering his Customer ID and password.

      1 Enter account details

    3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

      1 Payment confirmation

    4. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is a success

ItzCash Test Data

For ItzCash payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

ItzCash Payment Flow

    1. The customer enters his Email Address, Name and Permanent account number (PAN). Please note that for India the CustomerSocialSecurityNumber parameter consists of PAN. For more information about the PAN please click here.

      1 Enter customer details

    2. The customer logs in to his account by entering his Customer ID and password.

      1 Enter account details

    3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

      1 Payment confirmation

    4. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is a success

Credit Cards India Test Data

For Credit Cards India payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Credit Cards India Payment Flow

    1. The customer enters his Email Address, Name and Permanent account number (PAN). Please note that for India the CustomerSocialSecurityNumber parameter consists of PAN. For more information about the PAN please click here.

      1 Enter customer details

    2. The customer logs in to his account by entering his Customer ID and password.

      1 Enter account details

    3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

      1 Payment confirmation

    4. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is a success

Credit Cards Turkey Test Data

For Credit Cards Turkey payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Credit Cards Turkey Payment Flow

    1. The customer enters his Email Address, Name and Turkish Identification Number (ID). Please note that for Turkey the CustomerSocialSecurityNumber parameter consists of ID. For more information about the ID please click here.

      1 Enter customer details

    2. The customer logs in to his account by entering his Customer ID and password.

      1 Enter account details

    3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

      1 Payment confirmation

    4. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is a success

Santander Rio Test Data

For Santander Rio payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Santander Rio Payment Flow

  1. The customer enters his Email Address, Name and National Identity Document (DNI).
    Please note that for Argentina the Customer Social Security Number parameter consists of DNI. For more information about the DNI please click here.

    1 Enter customer details

  2. The customer logs in to his account by entering his Customer ID and password.

    1 Enter account details

  3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

    1 Payment confirmation

  4. The customer receives a message that the payment has been completed correctly.

    1 Payment confirmation

  5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Cash Payments Argentina Test Data

For Cash Payments Argentina payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Cash Payments Argentina Payment Flow

    1. The customer enters his Email Address, Name and National Identity Document (DNI), and chooses his preferred payment option from the given list. Please note that for Argentina the Customer Social Security Number parameter consists of DNI. For more information about the DNI please click here.

      1 Enter customer details

    2. The customer logs in to his account by entering his Customer ID and password.

      1 Enter account details

    3. The Customer checks the payment resume and proceeds with the payment by clicking on the Confirm button.

      1 Payment confirmation

    4. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is a success

Pay By Mobile Subscription

Below you will find a full example of a Pay by Mobile subscription request. The parameters of the payment are sent in the message body as a JSON object.

First, you need to make a one-off payment request containing the Preapproval Details parameters, that are specific for recurring payments, like:

  • MerchantPreapprovalID – Preapproval ID provided by merchant;
  • BillingFrequency – how often is the customer billed. It can be daily/weekly/monthly depending on the country and mobile carrier;
  • Duration – (optional) in units days/weeks/months – the billing period;
  • PreapprovalDescription – the subscription description which is displayed on the customer bill.

A 201 HTTP response (Created) is returned if the payment was correctly initialized.

For more information about status codes, please go to Basic HTTP Status Codes.

Request: 

POST https://paytest.smart2pay.com/v1/payments
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_0009",
    "Amount": 1000,
    "Currency": "EUR",      
    "MethodID": 79,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",   
     "Description": "Pay by mobile Recurring",   
    "Customer": {    
     "Email": "tester@smart2pay.com"   
    },
   "BillingAddress": {      
      "Country": "DE"
    },
    "PreapprovalDetails": {
       "MerchantPreapprovalID": 1122334455,
       "BillingFrequency": "Weekly",
       "Durantion": 10,
       "PreapprovalDescription": "Weekly subscription"
    }
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 2997294,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20170726151634",
    "MerchantTransactionID": "s2ptest_0009",
    "OriginatorTransactionID": null,
    "Amount": 1000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "Pay by mobile Recurring",
    "MethodID": 79,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30151,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 3668,
      "MerchantCustomerID": null,
      "Email": "tester@smart2pay.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 1517,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": null,
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 1,
    "Capture": null,
  "PreapprovalDetails": {
       "MerchantPreapprovalID": 1122334455,
       "BillingFrequency": "Weekly",
       "Durantion": 10,
       "PreapprovalDescription": "Weekly subscription"
    }, 
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=3BB3DAD6824F871A54FCA245C786F9C3.2997294"
  }
}

When the customer completes the subscription the first bill is also made. So you will receive a success notification that also contains a Preapproval ID which you will use to make automated recurring payments.

You need to respond with HTTP code 204 (No Content)!

Payment notification format:

Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "ID": 2997294,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20170726151634",
    "MerchantTransactionID": "s2ptest_0009",
    "OriginatorTransactionID": null,
    "Amount": 1000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "",
    "MethodID": 79,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30151,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 3668,
      "MerchantCustomerID": null,
      "Email": "tester@smart2pay.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 1517,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": 4182,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 1,
    "Capture": null,
    "PreapprovalDetails": null,
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=3BB3DAD6824F871A54FCA245C786F9C3.2997294"
  }
}

Response:

204 No Content

You can now initiate Recurring Payments, before each subscription’s billing date, based on the Preapproval ID received in the Notification for the first payment request.

Request: 

POST https://paytest.smart2pay.com/v1/payments/recurrent
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "PreapprovalID": 4182,
    "MerchantTransactionID": "Mobiles2ptest12345",
    "Amount": 1000,
    "Currency": "EUR",
    "MethodID": 79,
    "Description": "Mobile recurring payment",
    "BillingAddress": {
      "Country": "DE"
    } 
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
    "Payment": {
        "ID": 2997961,
        "SkinID": null,
        "ClientIP": null,
        "Created": "20170727064026",
        "MerchantTransactionID": " Mobiles2ptest12345",
        "OriginatorTransactionID": null,
        "Amount": 1000,
        "Currency": "EUR",
        "ReturnURL": null,
        "Description": "Mobile recurring payment",
        "MethodID": 79,
        "MethodOptionID": null,
        "IncludeMethodIDs": null,
        "ExcludeMethodIDs": null,
        "PrioritizeMethodIDs": null,
        "SiteID": 30151,
        "NotificationDateTime": null,
        "Customer": {
            "ID": 3668,
            "MerchantCustomerID": null,
            "Email": "",
            "FirstName": null,
            "LastName": null,
            "Gender": null,
            "SocialSecurityNumber": null,
            "Phone": null,
            "Company": null,
            "DateOfBirth": null
        },
        "BillingAddress": {
          "ID": 1517,
      	"City": null,
      	"ZipCode": null,
      	"State": null,
      	"Street": null,
      	"StreetNumber": null,
      	"HouseNumber": null,
      	"HouseExtension": null,
      	"Country": "DE"
    },
        "ShippingAddress": null,
        "Articles": null,
        "Details": null,
        "ReferenceDetails": null,
        "CustomParameters": null,
        "PreapprovalID": 4182,
        "Status": {
            "ID": 1,
            "Info": "Open",
            "Reasons": null
        },
        "MethodTransactionID": null,
        "TokenLifetime": null,
        "Capture": null,
        "PreapprovalDetails": null,
        "RedirectURL": null
    }
}

When the billing is successful you will receive a success notification.

Skrill Payment Request

Below you will find a full example of a one-off payment request for Skrill payment method (with Success and Bad response). The parameters of the payment are sent in the message body as a JSON object. Country and Description parameters are not mandatory, however it is highly recommended to be sent.

A 201 HTTP response (Created) is returned if the payment was correctly initialized.

For more information about status codes, please go to Basic HTTP Status Codes.

Request: 

POST https://paytest.smart2pay.com/v1/payments
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_a1_1",
    "Amount": 200,
    "Currency": "EUR",      
    "MethodID": 78,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",      
    "Description": "SKRILL test payment",
    "Customer": {    
      "Email": "skrill_user_test@smart2pay.com"   
    } ,
   "BillingAddress": {
      
      "Country": "DE"
    }
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 3356527,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20170929065639",
    "MerchantTransactionID": "s2ptest_a1_1",
    "OriginatorTransactionID": null,
    "Amount": 200,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "SKRILL test payment",
    "MethodID": 78,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30201,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 5126,
      "MerchantCustomerID": null,
      "Email": "skrill_user_test@smart2pay.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 420,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": null,
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 1,
    "Capture": null,
    "PreapprovalDetails": null,
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=5959D791A2EC38A7267170BA69CE51FE.3356527"
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://paytest.smart2pay.com/v1/payments
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_a1_1",
    "Amount": 200,
    "Currency": "EUR",      
    "MethodID": 78,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",      
    "Description": "SKRILL test payment",
    "Customer": {    
      "Email": "skrill_user_test@smart2pay.com"   
    } ,
   "BillingAddress": {
      
      "Country": "DE"
    }
  }
}

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": null,
    "SkinID": null,
    "ClientIP": null,
    "Created": null,
    "MerchantTransactionID": "s2ptest_a1_1",
    "OriginatorTransactionID": null,
    "Amount": 200,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "SKRILL test payment",
    "MethodID": 78,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": null,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 4298,
      "MerchantCustomerID": null,
      "Email": "skrill_user_test@smart2pay.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 420,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": null,
    "Status": {
      "ID": null,
      "Info": null,
      "Reasons": [
        {
          "Code": 20,
          "Info": "MerchantTransactionID is duplicated - s2ptest_a1_1"
        }
      ]
    },
    "MethodTransactionID": null,
    "TokenLifetime": null,
    "Capture": null,
    "PreapprovalDetails": null,
    "RedirectURL": null
  }
}

Skrill 1-TAP Payment Request

Below you will find a full example of a payment request for Skrill 1-TAP payment method with Success response. The parameters of the payment are sent in the message body as a JSON object. For 1-TAP payments the Preapproval Details parameters are mandatory to be sent in the initial payment request.

A 201 HTTP response (Created) is returned if the payment was correctly initialized.

For more information about status codes, please go to Basic HTTP Status Codes.

Request: 

POST https://paytest.smart2pay.com/v1/payments
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_a1_2",
    "Amount": 200,
    "Currency": "EUR",      
    "MethodID": 78,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",   
     "Description": "Skrill Initial OneTap Payment",   
    "Customer": {    
      "Email": "skrill_user_test@smart2pay.com"   
    } ,
   "BillingAddress": {
      
      "Country": "DE"
    },
    "PreapprovalDetails": {
      "PreapprovedMaximumAmount": 500,
       "MerchantPreapprovalID": 1122334455,
      "PreapprovalDescription": "Skrill 1tap payment"
    }
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 3356528,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20170929065825",
    "MerchantTransactionID": "s2ptest_a1_2",
    "OriginatorTransactionID": null,
    "Amount": 200,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "Skrill Initial OneTap Payment",
    "MethodID": 78,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30201,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 5127,
      "MerchantCustomerID": null,
      "Email": "skrill_user_test@smart2pay.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 420,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": null,
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 1,
    "Capture": null,
    "PreapprovalDetails": {
      "PreapprovedMaximumAmount": 500,
      "MerchantPreapprovalID": "1122334455",
      "PreapprovalDescription": "Skrill 1tap payment"
    },
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=DF7FF6371B1E775F3C385DF5E13E7164.3356528"
  }
}

After the payment request is completed, you will receive a notification from our system whether the payment is successful or not. The notification also contains the Preapproval ID which you need to use when you initiate recurring payments.

You need to respond with HTTP code 204 (No Content)!

Payment notification format:

Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Payment": {
    "ID": 3356528,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20170929065825",
    "MerchantTransactionID": "s2ptest_a1_2",
    "OriginatorTransactionID": null,
    "Amount": 200,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "Skrill Initial OneTap Payment",
    "MethodID": 78,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30201,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 5127,
      "MerchantCustomerID": null,
      "Email": "skrill_user_test@smart2pay.com",
      "FirstName": "aaa",
      "LastName": "bbb",
      "Gender": null,
      "SocialSecurityNumber": "65845362385",
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": {
      "ID": 420,
      "City": null,
      "ZipCode": null,
      "State": null,
      "Street": null,
      "StreetNumber": null,
      "HouseNumber": null,
      "HouseExtension": null,
      "Country": "DE"
    },
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": null,
    "CustomParameters": null,
    "PreapprovalID": 4182,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 1,
    "Capture": null,
    "PreapprovalDetails": null,
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=DF7FF6371B1E775F3C385DF5E13E7164.3356528"
  }
}

Response:

204 No Content

You will also receive a notification for the successful status of the Preapproval that you also need to answer with 204 NoContent!

Payment notification format:

Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
  "Preapproval": {
    "ID": 4182,
    "Created": "20170726151634",
    "MethodID": 78,
    "SiteID": 30201,
    "MerchantPreapprovalID": "1122334455",
    "RecurringPeriod": 0,
    "PreapprovedMaximumAmount": null,
    "Currency": null,
    "ReturnURL": null,
    "Description": "Skrill 1tap payment",
    "Customer": null,
    "BillingAddress": null,
    "Status": {
      "ID": 2,
      "Info": "Open",
      "Reasons": null
    },
    "RedirectURL": null,
    "MethodOptionID": 0
  }
}

Response:

204 No Content

You can now initiate Recurring Payments based on the Preapproval ID received in the Notification. We also recommend you to send the Description parameter.

Request: 

POST https://paytest.smart2pay.com/v1/payments/recurrent
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

{
 "Payment": {
   "PreapprovalID": 4182,
   "MerchantTransactionID": "s2ptest_1122",
   "Amount": 100,
   "Currency": "EUR",
   "MethodID": 78,
   "Description": "1tap recurrent payment",
   "Customer": {  
     "Email" : "skrill_user_test@smart2pay.com"
    }
   }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
    "Payment": {
        "ID": 3356528,
        "SkinID": null,
        "ClientIP": null,
        "Created": "20170929064026",
        "MerchantTransactionID": "s2ptest_1122",
        "OriginatorTransactionID": null,
        "Amount": 100,
        "Currency": "EUR",
        "ReturnURL": null,
        "Description": "1tap recurrent payment",
        "MethodID": 78,
        "MethodOptionID": null,
        "IncludeMethodIDs": null,
        "ExcludeMethodIDs": null,
        "PrioritizeMethodIDs": null,
        "SiteID": 30201,
        "NotificationDateTime": null,
        "Customer": {
            "ID": 5127,
            "MerchantCustomerID": null,
            "Email": "skrill_user_test@smart2pay.com",
            "FirstName": null,
            "LastName": null,
            "Gender": null,
            "SocialSecurityNumber": null,
            "Phone": null,
            "Company": null,
            "DateOfBirth": null
        },
        "BillingAddress": null,
        "ShippingAddress": null,
        "Articles": null,
        "Details": null,
        "ReferenceDetails": null,
        "CustomParameters": null,
        "PreapprovalID": 4182,
        "Status": {
            "ID": 2,
            "Info": "Success",
            "Reasons": null
        },
        "MethodTransactionID": null,
        "TokenLifetime": null,
        "Capture": null,
        "PreapprovalDetails": null,
        "RedirectURL": null
    }
}

To cancel an 1-TAP subscription, you must send a DELETE action for an existing preapproval object. For more information about closing a preapproval please go to our section Close a Preapproval.

Credit Cards Uruguay Test Data

For Credit Cards Uruguay payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Credit Cards Uruguay Payment Flow

    1. The customer enters his Email Address, Name and Identity Card (CI). Please note that for Uruguay the Customer Social Security Number parameter consists of Identity Card (CI). For more information about the CI please click here.

      1 Enter customer details

    2. The customer enters his email address, name and card details: Card Number, CVC (CSC) and Expiration Date. He finalizes the payment by using the Pay button.

      1 Enter card details

    3. The customer receives a message that the payment has been completed correctly.

      1 Payment confirmation

    4. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is Processing

Redpagos Test Data

For Redpagos payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Redpagos Payment Flow

    1. The customer enters his Email Address, Name and Identity Card (CI). Please note that for Uruguay the Customer Social Security Number parameter consists of Identity Card (CI). For more information about the CI please click here.

      1 Enter customer details

    2. The customer receives a message that the payment has been initiated successfully together with the payment instructions. In order to complete the payment, he needs to know the voucher number and pay it at any Redpagos branch in his area.

      1 Enter card details

    3. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

      1 Return page when the redirection status is Processing

Credit Cards Argentina Test Data

For Credit Cards Argentina payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Credit Cards Argentina Payment Flow

  1. The customer enters his Email Address, Name and National Identity Document (DNI). Please note that for Argentina the Customer Social Security Number parameter consists of National Identity Document (DNI)! For more information about the DNI please click here.

    1 Enter customer details

  2. The customer enters his name and card details: Card Number, CVC (CSC) and Expiration Date, and finalizes the payment by using the Pay button.

    1 Enter card details

  3. The customer receives a message that the payment has been completed correctly.

    1 Payment confirmation

  4. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

SEPA Direct Debit Test Data

For SEPA Direct Debit payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

SEPA Direct Debit Payment Flow

    1. Make a Preapproval request to initiate a Direct Debit mandate with all the mandatory parameters (including Customer Name, Email and Address).

    2. The Customer is redirected to the Provider’s page to fill the IBAN Number:

      1 Iban Number required

    3. The Customer fills the phone number:

      1 Phone number required

    4. The Customer confirms the mandate using the 4-DIGIT CODE SMS code received:

      1 4-DIGIT CODE SMS

    5. The Customer is redirected back to the Merchant website:

      1 Preapproval ReturnURL

    6. The Customer receives the digital signed mandate via email:

      1 Received digital signed mandate

    7. You will receive a notification from our system which needs to be answered with 204 NoContent.

      Based on the PreapprovalID, Direct Debits can be initiated.

Get a list of filtered payments

You can specify various filters as parameters in the query string in order to get a customized list of payments. This type of request allows you to get a list of payments according to your own needs and requirements, simplifying the process of finding transactions.

You can get a list of paginated payments by adding the pageSize and pageIndex parameters to the URL. The pageIndex parameter is recommended to be used together with the pageSize parameter to select the number of transactions on a specific page.

The following table describes all the filters that you can use. Please note that you can mix the filters to get specific results.

FILTERS
Field Description Data type
pageSize The maximum number of transactions that will be returned per page. The pageSize parameter used together with the pageIndex parameter will also represent the number of transactions returned for a specific page. Please note that without specifying any parameter the default number of transactions that will be returned is 50! Long
Request:
GET https://paytest.smart2pay.com/v1/payments?pagesize=20&pageindex=3
pageIndex Using the pageIndex parameter you will be able to receive the transactions paginated. The default number of transactions that will be returned per page is 50. Transactions are ordered by ID descending. The pageIndex parameter is recommended to be used together with the pageSize parameter in order to choose the desired number of transactions returned per page. Long
Request:
GET https://paytest.smart2pay.com/v1/payments?pagesize=20&pageindex=3
sortDirection By default, the transactions are ordered by ID descending. By using the sortDirection parameter, you have the possibility to order the transactions by ID ascending (sortdirection=asc). String
Request:
GET https://paytest.smart2pay.com/v1/payments?pagesize=20&pageindex=3&sortdirection=asc
sortBy By default, the transactions are ordered by ID descending. By using the sortBy parameter you will be able to receive the transactions sorted after merchanttransactionid / inputdatetime / amount in combination with sortDirection (=asc / =desc) parameter. Long
Request:
GET https://paytest.smart2pay.com/v1/payments?pagesize=20&pageindex=3&sortby=amount&sortdirection=asc
startDate The date and time after which the payments are returned. DateTime

YYYYMMDDHHMMSS

Request:
GET https://paytest.smart2pay.com/v1/payments?startDate=20170803150000
endDate The date and time until which the payments are returned. DateTime

YYYYMMDDHHMMSS

Request:
GET https://paytest.smart2pay.com/v1/payments?startDate=20170803150000&endDate=20171003140000
methodID Only the transactions having this methodID will be returned. Long
Request:
GET https://paytest.smart2pay.com/v1/payments?methodID=2
country Only the transactions having this country code will be returned. String

(ISO 3166-1-alpha-2)

Request:
GET https://paytest.smart2pay.com/v1/payments?country=NL
currency Only the transactions having this currency code will be returned. String

(ISO 4217)

Request:
GET https://paytest.smart2pay.com/v1/payments?currency=EUR
minimumAmount Only the payments with an amount higher than this will be returned. Integer (last 2 digits representing the decimal part)
Request:
GET https://paytest.smart2pay.com/v1/payments?minimumAmount=100
maximumAmount Only the payments with an amount lower than this will be returned. Integer (last 2 digits representing the decimal part)
Request:
GET https://paytest.smart2pay.com/v1/payments?maximumAmount=1000
merchantTransactionID Only the payment having this merchantTransactionID will be returned. String

^[0-9a-zA-Z_-]{1,50}$

Request:
GET https://paytest.smart2pay.com/v1/payments?merchantTransactionID=123456
statusID Only the transactions having this statusID will be returned. Integer

The ID of the payment status can have the following values: 1 – Open, 2 – Success, 3 – Cancelled, 4 – Failed, 5 – Expired, 9 – Authorized.

Request:
GET https://paytest.smart2pay.com/v1/payments?statusID=2
methodTransactionID Only the payments having this methodTransactionID will be returned. This transaction ID from the payment method provider can be used for customer support. String

^[0-9a-zA-Z_-]{1,50}$

Request:
GET https://paytest.smart2pay.com/v1/payments?methodTransactionID=100200
typeID Only the transactions having this typeID will be returned. Integer

The typeID filter can have the following values: 1 – Payments, 2 – Recurring payments.

Request:
GET https://paytest.smart2pay.com/v1/payments?typeID=1

Here is an example request where the transactions are divided in pages (groups of transactions) of 2 transactions and the third group of transactions is returned.

Request:

GET https://paytest.smart2pay.com/v1/payments?pagesize=2&pageindex=3

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{
"Payments": [
  {
   "ID": 2459122,
   "SkinID": null, 
   "Created": "20160411140447",
   "MerchantTransactionID": "WPD_1460383484_8795_5000",
   "Amount": 100,
   "Currency": "BAM",
   "ReturnURL": "https://docs.smart2pay.com/wp-content/plugins/smart2pay-api/views/funcs/demo_clean_return.php",
   "Description": null,
   "MethodID": 79,
   "MethodOptionID": null,
   "IncludeMethodIDs": null,
   "ExcludeMethodIDs": null,
   "PrioritizeMethodIDs": null,
   "SiteID": 30201,
   "NotificationDateTime": "20160411140522",
   "Customer": null,
   "BillingAddress": null,
   "ShippingAddress": null,
   "Articles": null,
   "Details": null,
   "ReferenceDetails": null,
   "CustomParameters": null,
   "PreapprovalID": null,
   "Status": {
     "ID": 1,
     "Info": "Open",
     "Reasons": null
   },
   "MethodTransactionID": null,
   "TokenLifetime": null,
   "Capture": null,
   "RedirectURL": null
   },
   {
   "ID": 2459118,
   "SkinID": null,
   "Created": "20160411125607",
   "MerchantTransactionID": "WPD_1460379365_1783_6355",
   "Amount": 1100,
   "Currency": "NGN",
   "ReturnURL": "https://docs.smart2pay.com/wp-content/plugins/smart2pay-api/views/funcs/demo_clean_return.php",
   "Description": null,
   "MethodID": null,
   "MethodOptionID": null,
   "IncludeMethodIDs": null,
   "ExcludeMethodIDs": null,
   "PrioritizeMethodIDs": null,
   "SiteID": 30201,
   "NotificationDateTime": "20160411125629",
   "Customer": null,
   "BillingAddress": null,
   "ShippingAddress": null,
   "Articles": null,
   "Details": null,
   "ReferenceDetails": null,
   "CustomParameters": null,
   "PreapprovalID": null,
   "Status": {
     "ID": 3,
     "Info": "Cancelled",
     "Reasons": null
       },
   "MethodTransactionID": null,
   "TokenLifetime": null,
   "Capture": null,
   "PreapprovalDetails": null,
   "RedirectURL": null
    }
  ],
   "TotalPages": 50,
   "PageSize": 2,
   "PageIndex": 3,
   "Count": 2,
   "TotalCount": 100
}

In the response you will receive additional information in order to keep track of your transactions, like: TotalPages, PageSize, PageIndex, Count and TotalCount.

Here is the example of the request where the transactions are divided in pages (groups of transactions) of 3 transactions and the last group of transactions is returned. In this case the Count parameter will refer to the number of the remaining transactions on the last page.

Request:

GET https://paytest.smart2pay.com/v1/payments?pagesize=3&pageindex=50

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8
{
  "Payments": [
    {
      "ID": 3037285,
      "SkinID": null,
      "ClientIP": null,
      "Created": "20170808100902",
      "MerchantTransactionID": "WPD_1502186809_5528_8717",
      "OriginatorTransactionID": null,
      "Amount": "1",
      "Currency": "PHP",
      "ReturnURL": "https://docs.smart2pay.com/wp-content/plugins/smart2pay-api/views/funcs/demo_clean_return.php",
      "Description": null,
      "MethodID": 1029,
      "MethodOptionID": null,
      "IncludeMethodIDs": null,
      "ExcludeMethodIDs": null,
      "PrioritizeMethodIDs": null,
      "SiteID": 30201,
      "NotificationDateTime": "20170808100927",
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Details": null,
      "ReferenceDetails": null,
      "CustomParameters": null,
      "PreapprovalID": null,
      "Status": {
        "ID": 3,
        "Info": "Cancelled",
        "Reasons": null
      },
      "MethodTransactionID": null,
      "TokenLifetime": null,
      "Capture": null,
      "PreapprovalDetails": null,
      "RedirectURL": null
    },
    {
      "ID": 3037282,
      "SkinID": null,
      "ClientIP": null,
      "Created": "20170808100848",
      "MerchantTransactionID": "WPD_1502186795_5903_4452",
      "OriginatorTransactionID": null,
      "Amount": "1",
      "Currency": "PHP",
      "ReturnURL": "https://docs.smart2pay.com/wp-content/plugins/smart2pay-api/views/funcs/demo_clean_return.php",
      "Description": null,
      "MethodID": 1051,
      "MethodOptionID": null,
      "IncludeMethodIDs": null,
      "ExcludeMethodIDs": null,
      "PrioritizeMethodIDs": null,
      "SiteID": 30201,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Details": null,
      "ReferenceDetails": null,
      "CustomParameters": null,
      "PreapprovalID": null,
      "Status": {
        "ID": 4,
        "Info": "Failed",
        "Reasons": null
      },
      "MethodTransactionID": null,
      "TokenLifetime": null,
      "Capture": null,
      "PreapprovalDetails": null,
      "RedirectURL": null      
        }
     ],
      "TotalPages": 50,
      "PageSize": 3,
      "PageIndex": 50,
      "Count": 2,
      "TotalCount": 149
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Please note that when a request is initiated with PageIndex filter greater than the TotalPages, an HTTP 4xx status is returned with return code 184: PageIndex Out of Range!

Request:

GET https://paytest.smart2pay.com/v1/payments?pagesize=20&pageindex=500

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Payments": [],
  "Count": 0,
  "TotalPages": 178,
  "TotalCount": 3552,
  "PageIndex": 500,
  "PageSize": 20,
  "Error": "PageIndex Out of Range"
}

Refund Details

Go to Refunds tab from the dashboard and use the search filters to find a specific refund. After you have found the transaction you have been looking for, using the search filters, just double click on it to see specific details of that payment.

A new window will open containing the general details for that Payment ID and also providing details about specific sections, like: General information, Reporting, Initial Payment details and Invoicing.

The dashboard Refund Details allows the user to always find specific information in order to be informed and keep track of his day-to-day transactions and refunds.

General provides detailed information for the following fields: ID of the transaction, Initial Payment ID, Input Date Time, Merchant ID, Merchant Site ID, Method ID, Merchant Alias, Merchant Site Alias, Method Name, Amount, Currency, Status, Merchant Transaction ID, Originator Transaction ID, Type, Description, Specific Details, Method Transaction ID.

32

Reporting provides detailed information for the following fields: Notification Date Time, Last Notified Status.

32

InitialPayment provides detailed information for the following fields: ID, Merchant Transaction ID, Input Date Time, Amount, Currency, Status, Available Amount, Method ID, Method Name, Country.

32

Invoicing provides detailed information for the following fields: Invoiced as refund on, Gross Settlement Amount, Settlement Currency, Exchange Rate, Refund Fee, VAT.

32

  • For refunds of credit card transactions there will be displayed specific sections and fields, like: the ReturnCodes section.

General provides detailed information for the following fields: ID of the transaction, Initial Payment ID, Input Date Time, Merchant ID, Merchant Site ID, Method ID, Merchant Alias, Merchant Site Alias, Method Name, Amount, Currency, Status, Merchant Transaction ID, Originator Transaction ID, Description, Statement Descriptor, Specific Details, Method Transaction ID.

32

Reporting provides detailed information for the following fields: Notification Date Time, Last Notified Status.

32

ReturnCodes provides detailed information for the following fields: Return Code, Return Code Description.

32

Initial Payment provides detailed information for the following fields: ID, Merchant Transaction ID, Input Date Time, Amount, Currency, Status, Available Amount, Method ID, Method Name, Country.

32

Invoicing provides detailed information for the following fields: Invoiced as refund on, Gross Settlement Amount, Settlement Currency, Exchange Rate, Refund Fee, VAT.

32

Payment Details

Go to Payments tab from the dashboard and use the search filters to find a specific payment. After you have found the transaction you have been looking for, using the search filters, just double click on it to see specific details of that payment.

A new window will open containing the general details for that Payment ID and also providing details about specific sections, like: General information, Reporting, Flags, Return Codes and Invoicing.

Please note that Credit Card, 3D Secure, Fraud Check sections are specific and will only appear for credit card transactions!

The dashboard Payment Details allows the user to always find specific information in order to be informed and keep track of his day-to-day operations and transactions.

General provides detailed information for the following fields: ID of the transaction, Merchant Transaction ID, Input Date Time, Merchant ID, Merchant Site ID, Method ID, Merchant Alias, Merchant Site Alias, Method Name, Amount, Currency, Status, Available Amount, Return URL, Description, Originator Transaction ID, Customer Name, Customer Email, Country, Specific Details, Method Transaction ID.

32

Reporting provides detailed information for the following fields: Notification Date Time, Last Notified Status.

32

Flags provides detailed information for the following fields: Request Version, Request Type ID.

32

Return Codes provides detailed information for the following fields: Return Code, Provider Return Code.

32

Invoicing provides detailed information for the following fields: Invoiced as attempt on, Invoiced as success on, Merchant Amount, Merchant Currency, Gross Settlement Amount, Settlement Currency, Exchange Rate, Transaction Fee, General Fee, Issued Fee, Attempt Fee, LocalVat Fee, Repatriation Fee, VAT.

32

  • For credit card transactions there will be displayed a few specific sections and fields, like: Credit Card, 3D Secure, Fraud Check sections.

General provides detailed information for the following fields: ID of the transaction, Merchant Transaction ID, Input Date Time, Merchant ID, Merchant Site ID, Method ID, Merchant Alias, Merchant Site Alias, Method Name, Amount, Currency, Status, Available Amount, Captured Amount, Return URL, Description, Statement Descriptor, Originator Transaction ID, Country, Language, Specific Details, Method Transaction ID.

32

Credit Card provides detailed information for the following fields: Masked Card Number, Card Expiration Month, Card Expiration Year, Card Holder Name, Credit Card Brand, Credit Card Sub-Brand, Credit Card Token.

32

3DSecure provides detailed information for the following fields: 3D Secure Check, 3D Secure CAVV, 3D Secure ECI.

32

Fraud Check provides detailed information for the following fields: Fraud Status Code, Fraud Score, Fraud Status ID, Fraud Response Description, Fraud Response Code, Fraud Counter, Fraud Check Mode.

32

Reporting provides detailed information for the following fields: Notification Date Time, Last Notified Status, Reported As Authorized Date, Reported As Captured Date, Reported As Charged Back Date.

32

Flags provides detailed information for the following fields: Request Version, Capture, Retry Counter,

32

Return Codes provides detailed information for the following fields: Return Code, Return Code Description.

32

Dispute provides detailed information for the following fields: ID of the transaction, Status, Notification Date Time, Last Notified Status, Amount, Currency, Dispute Date Time, Created Date Time, Reason Code, Reason Code Name.

32

Invoicing provides detailed information for the following fields: Invoiced as attempt on, Invoiced as success on, Gross Settlement Amount, Settlement Currency, Exchange Rate, Transaction Fee, General Fee, Issued Fee, Attempt Fee, LocalVat Fee, Repatriation Fee, VAT.

32

Card Processing Return Codes

When an API error occurs, an HTTP 4xx or HTTP 5xx status is returned with a code that provides more detailed information in the response.

List of possible Return Code IDs for credit card transactions:

  • 1: Invalid data
  • 2: Validation failed
  • 13: Generic error
  • 17: Payment is invalid
  • 20: MerchantTransactionID is duplicated
  • 100: Invalid route
  • 293: Transaction rejected by fraud provider
  • 1000: Payment.MerchantTransactionID is invalid
  • 1001: Payment.Amount is invalid
  • 1002: Payment.Currency is invalid
  • 1003: Payment.ReturnURL is invalid
  • 1004: Payment.Description is invalid
  • 1005: Payment.StatementDescriptor is invalid
  • 1006: CardDetails.HolderName is invalid
  • 1007: CardDetails.Number is invalid
  • 1008: CardDetails.ExpirationMonth is invalid
  • 1009: CardDetails.ExpirationYear is invalid
  • 1010: CardDetails.SecurityCode is invalid
  • 1011: CardDetails – Card is expired
  • 1012: Address.City is invalid
  • 1013: Address.ZipCode is invalid
  • 1014: Address.State is invalid
  • 1015: Address.Street is invalid
  • 1016: Address.StreetNumber is invalid
  • 1017: Address.HouseNumber is invalid
  • 1018: Address.HouseExtension is invalid
  • 1019: Address.CountryCode is invalid
  • 1020: Address.Country does not exist
  • 1021: Customer.MerchantCustomerID is invalid
  • 1022: Customer.Email is invalid
  • 1023: Customer.Firstname is invalid
  • 1024: Customer.Lastname is invalid
  • 1025: Customer.Gender is invalid
  • 1026: Customer.SocialSecurityNumber is invalid
  • 1027: Customer.Phone is invalid
  • 1028: Customer.Company is invalid
  • 2400: Token is invalid
  • 2401: Token value is not available
  • 2402: Token usage limit exceeded
  • 2403: Credit card invalid for the token
  • 2404: Missing token details
  • 2600: Missing credit card details
  • 5001: AVS Mismatch Failure
  • 5002: AVS Mismatch Failure
  • 5003: CVV2 Mismatch Failure
  • 5004: Sorry, the transaction failed Cybersource Fraud Test and was voided
  • 5005: Transaction may not be marked
  • 5006: orderID was not marked successfully
  • 5007: Test Tran. Bad Card
  • 5008: Test Tran. Problem
  • 5009: Username already exists
  • 5010: Username is blank
  • 5011: Fraud Screen Failure
  • 5012: Missing PIN Code
  • 5013: Invalid Bank Acct. No.
  • 5014: Invalid Bank Routing No.
  • 5015: Invalid/Missing Check No.
  • 5016: Invalid card for test transaction
  • 5017: Invalid CVV2/CVC2 No.
  • 5018: Expired card
  • 5019: Missing Data
  • 5020: Missing Email Address
  • 5021: Zip Code does not match Billing State
  • 5022: Invalid Billing Zip Code
  • 5023: Zip Code does not match Shipping State
  • 5024: Invalid Shipping Zip Code
  • 5025: Invalid Credit Card CVV2/CVC2 Format
  • 5026: Maximum number of attempts has been exceeded
  • 5027: Credit Card number has been flagged and can not be used to access this service
  • 5028: IP Address is on Blocked List
  • 5029: Billing country does not match ipaddress country
  • 5030: US based ipaddresses are currently blocked
  • 5031: Credit Cards issued from this country are currently not being accepted
  • 5032: Credit Cards issued from this bank are currently not being accepted
  • 5033: Daily volume exceeded
  • 5034: Too many transactions within allotted time
  • 5035: Sales for this phone number are currently not being accepted
  • 5036: Email Address is on Blocked List
  • 5037: Duplicate Transaction error
  • 5038: Missing/incorrect password
  • 5039: Account not configured for mobil administration
  • 5040: IP Not registered to username
  • 5041: Mode not permitted for this account
  • 5042: Currently Blank
  • 5043: Currently Blank
  • 5044: Processor not responding
  • 5045: Missing merchant/publisher name
  • 5046: Currently Blank
  • 5047: Discount exceeds available gift certificate balance
  • 5048: Gift certificate discount does not match order
  • 5049: Capture failed but will retry again later
  • 5050: Cancel failed but will retry again later
  • 5051: Refund failed at provider
  • 5052: Security code (CVV2/CVC2) is incorrect
  • 5053: Do not Honour
  • 5054: Not sufficient funds
  • 5055: Invalid card number
  • 5056: Merchant does not allow card to be sent
  • 5057: The merchant does not allow Card on File operations
  • 5058: Card temporarily blocked by issuing bank or under suspicion of fraud
  • 5059: Rejection without specifying motive
  • 5060: Operation not allowed for this type of card
  • 5061: Invalid transaction card / issuer / acquirer
  • 5062: Operation rejected to avoid duplicities
  • 5063: Transaction not permitted on card
  • 5064: Technical error upstream processor/gateway
  • 5065: Card not found within table of ranges
  • 5066: Pickup Card
  • 5067: Decline Cvv2 failure
  • 5068: Issuer not available
  • 5069: Card brand not accepted
  • 5070: Wrong Expiration Date
  • 5071: Restricted card

Klarna Payments Test Data

In order for you to test Klarna Payments payment method successfully, please use the below test data.

Klarna Payments Test Data
Data Value
Country: United Kindom (GB) United States of America (US)
Currency: GBP USD
Email: youremail@email.com youremail@email.com
First Name: Doe Doe
Last Name: Test Test
Phone Number: +440745785615 863-869-1164
Article Type: 4 = Discount, 5 = Physical, 6 = Shipping_fee, 7 = Sales_tax, 8 = Digital, 9 = Gift_card, 10 = Store_credit, 11 = Surcharge

Klarna Payments Payment Flow

  1. The Customer fills the form with his personal details. For test purposes, please use the above test data depending on the country used. The Customer is then redirected to Klarna’s info and Terms &Conditions page where he needs to click on Buy button.

    1 Enter payment details

  2. If email, name or either phone is not sent, the customer will need to provide this info on a intermediary page. Please note that if Shipping Address is not sent than by default it will have the same value as Billing Address.

    1 Enter details

  3. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Hong Leong Connect PEx+ Test Data

For Hong Leong Connect PEx+ payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Hong Leong Connect PEx+ Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer logs in to his Connect mobile app on his smartphone by entering his password, scans the QR code and confirms the payment.

    1 Account login

UOB Online Test Data

For UOB Online payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

UOB Online Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with UOB Online.

    1 Payment details

  3. The customer logs in to his UOB account by entering his User ID and password, and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Bank Islam Online Test Data

For Bank Islam Online payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Bank Islam Online Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Bank Islam Online.

    1 Payment details

  3. The customer logs in to his account by entering his User ID and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

myBSN Test Data

For myBSN payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

myBSN Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with myBSN.

    1 Payment details

  3. The customer logs in to his account by entering his Username and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

AffinOnline Test Data

For AffinOnline payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

AffinOnline Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with AffinOnline.

    1 Payment details

  3. The customer logs in to his AffinOnline account by entering his Username and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Bank Rakyat Internet Banking Test Data

For Bank Rakyat Internet Banking payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Bank Rakyat Internet Banking Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Bank Rakyat Internet Banking.

    1 Payment details

  3. The customer logs in to his Rakyat Internet Banking account by entering his Username and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Celcom AirCash Test Data

For Celcom AirCash payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Celcom AirCash Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Celcom AirCash by entering his registered mobile number.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Public Bank Online Test Data

For Public Bank Online payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Public Bank Online Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Public Bank Online.

    1 Payment details

  3. The customer logs in to his Public Bank Online account by entering his User ID and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Credit Card Processing

Accepting all major credit cards for your business is essential in today’s economic environment and we have made it easier for you now than ever.

With our reliable and easy to integrate platform – GlobalPay REST API, we offer our clients two ways to accept credit card payments: Redirect Card Processing and Direct Card Processing.

Compare credit card payment solutions
Features Redirect Card Processing Direct Card Processing
PCI compliance required No Yes
Credit card tokenization Yes Yes
Card details collected by merchant No Yes
One click payment Yes Yes
Payment page skinning and branding allowed Yes Yes
Customers pay never leaving your website No Yes
Instant payment status notification Yes Yes
Retry logic Yes Yes
Processing transactions in local currencies Yes Yes
Advanced payment security solutions Yes Yes

Redirect Card Processing

Benefits:

  • Even though you are not PCI compliant, you can still process credit cards. Redirect Card Processing comes to your aid and takes care of PCI compliance for you.
  • Not having to worry about being PCI compliant, gives you time to focus on the other aspects of your business.
  • By integrating Redirect Card Processing you have access to many alternative payment options including Credit Card processing.
  • Customer satisfaction is higher because customers expect to be able to pay with their preferred method of payment. Providing various payment options is essential and an invaluable tool for ensuring customer service. For a complete list of our payment methods available, please go to Payment Methods API section.

Direct Card Processing

Benefits:

  • If you are only interested in processing credit cards and you are PCI compliant, this is the best solution for you.
  • With a singular reliable payment option: Direct Card Processing, you can run your business 24/7, focusing on a single payment method.
  • By integrating Direct Card Processing you have access to credit card payment method with a frictionless payment flow.
  • With Direct Card processing, the payment process is more efficient and less time consuming. You will complete transactions more quickly and easily, without any intermediary page.

In order for you to accept credit card payments and handling card data directly, no matter the size or number of transactions, you must comply with the PCI DSS (Payment Card Industry Data Security Standards).

Take into consideration when choosing the card processing solution that you should be PCI compliant if you wish to accept Direct Card Processing. If you are not fully PCI compliant, you need to use Redirect Card Processing.

Get a list of preapprovals

You can get information about all the Preapprovals you have created per SiteID by using an action based on GET HTTP request. Please be aware that only a limited amount of details for each preapproval will be provided.

The default number of preapprovals returned by this request is 50, but you can get a customized list of preapprovals by adding the limit parameter to the URL.

Definition: GET /v1/preapprovals

Request:

GET https://paytest.smart2pay.com/v1/preapprovals
Authorization: Basic MzAyMDE6aEo1Um9iWXg5cjdGZk53Q3ZIWTlMWEhxcXIrRkV6cmM3YUp2UVFrNEdhejFtZzdSeXk=

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Preapprovals": [
    {
      "ID": 4217,
      "Created": "20170804065155",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_g107",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription update1",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 2,
        "Info": "Open",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 4103,
      "Created": "20170714123423",
      "MethodID": 78,
      "SiteID": 30201,
      "MerchantPreapprovalID": "1122991392222",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": "500",
      "Currency": "EUR",
      "ReturnURL": null,
      "Description": "PreapprovalDescription",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 2,
        "Info": "Open",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 1744,
      "Created": "20160913144228",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_f25",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription update1",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 4,
        "Info": "ClosedByCustomer",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 1743,
      "Created": "20160913120451",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_f23",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 4,
        "Info": "ClosedByCustomer",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    }
  ]
}

Method Balance

By accessing the Method Balance tab, you can see for each method the converted balance from the transaction (merchant) currency to the settlement currency in the calculated amount field.

Please note that the converted balance value from the calculated amount field is an approximate value based on the current exchange rate.

This means, you have the possibility to see the currency and the amount for a specific method in which you have initiated the payment and the amount for that specific method in the settlement currency.

84

Search filters

When you access the Method Balance tab, the Search Filters section is expanded. In order to collapse it just click the arrow on the right of the screen.

84

You can search methods by using the following filters:

  • Method Name: the name of the payment method used and assigned for a specific settlement cycle;
  • Merchant Currency: the currency in which the merchant has made the payment;
  • Settlement Currency: the currency in which the settlement will be made.

84

Invoices

By accessing the Invoices tab, you can see all of your invoices and when they were generated. You can also search and view a specific invoice by introducing either the invoice number or the total amount in the appropriate text boxes.

You have the possibility to download a specific invoice or to download all of the invoices into the appropriate format. Invoices will be sent on email and, on request, they can also be generated in CSV format in SFTP.

84

Search filters

When you access the Invoices tab, the Search Filters section is expanded. In order to collapse it just click the arrow on the right of the screen.

84

You can also search invoices by using the following filter:

  • Interval: the time period in which a specific invoice was generated.

WeChat Test Data

For WeChat payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

WeChat Payment Flow

  1. The customer selects his preferred currency from the list and enters his email address.

    1 Enter email

  2. You can skip this step by sending in the initial POST the following parameters: SkipHPP=1 and CustomerEmail.

  3. The Customer is redirected to WeChat payment page.

    1 WeChat payment page

  4. The Customer opens WeChat application and scans the QR code.

    1 QR code scanning

  5. The payment details are displayed and the customer confirms by using the payment password.

    1 Payment confirmation

  6. The payment is confirmed.

    1 Payment successful

  7. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

Testing Requirements

Test Amounts

Before going live you will first complete a number of test card transactions on our test environment. We have provided a range of amounts that you can use to check all the transactional statuses. Using the below amounts will produce specific responses in order for you to test different scenarios.

Please be aware that all the possible statuses of the transactions that are returned in responses are based on the values assigned in the Amount field. If you want to obtain a specific status, simply enter a specific amount as the transaction amount. Below you will find different amounts to simulate certain situations and statuses.

The amount’s last two digits represent the decimal part (11.54 will be sent 1154).

Test Amounts
Value Status Description
1 – 10000 Captured / Authorized For this amount range all the actions will be successful: payment authorization, capture action, cancel action, refund action.
10001 Failed All the transactions having this amount will fail.
10002 QueuedForCapturing

If you set capture flag to true it will return status QueuedForCapturing with return code: 5288: “Capture failed but will retry again later”.

If you set capture flag to false it will return status Authorized. Then if you sent a capture request it will receive status QueuedForCapturing with return code: 5288: “Capture failed but will retry again later”.

10003 CaptureRequested

If you set capture flag to true it will return status CaptureRequested.

If you set capture flag to false it will return status Authorized. Then if you sent a capture request it will receive status CaptureRequested.

10004 Transaction: Captured; Refund: Open If this amount will be used for a transaction it will be captured but the refund will remain Open.
10005 Failed Capture failed with timelimit reached. The timelimit for capture action is overdue.
10006 QueuedForCanceling If you set capture flag to false it will return status Authorized. Then if you sent a cancel request it will receive status QueuedForCanceling with return code: 5289: “Cancel failed but will retry again later”.
10201 – 10299 Transaction: Captured; Refund: Failed If any of the amounts in this range limit are used for a transaction it will be Captured but the refund will fail.
20001 – 30000 Failed If any of the amounts in this range limit are used for a transaction it will fail and it will receive status Failed with return code: 5291: “Security code (CVV2/CVC2) is incorrect”.
30001 – 30200 Captured / Authorized For this amount range all the actions will be successful: payment authorization, capture action, cancel action, refund action. For the initial request there is a delay in seconds according to the last 3 digits (from 1 – 200 seconds).

Test Credit Card Numbers

For testing purposes, please use the following credit card numbers:

Test Credit Card Numbers
Credit Card Name Credit Card Number
Visa: 4111111111111111
4024007189870784
Mastercard: 5148196509775860
5443066050671259
Discover: 6011087785272940
6011235328768235
UnionPay: 6226388000000095
6216261000000000018
Visa Electron: 5443066050671259
4917300800000000
American Express: 345364891980314
372986503275489
Diners Club: 30120905411096
38341714925074
Hipercard: 6062825624254001
JCB: 3158178601355868
210076836080396
InstaPayment: 6385756289989351
6390524121376333

For testing purposes, please use only the credit card numbers from the above list! If any other credit card number is used for a test transaction it will fail and it will receive status Failed with return code: 5287: “Invalid card for test transaction”.

Card Processing Status Codes

List of transaction status IDs
Status ID Name Description Final Status Applicable for
1 Open The transaction is initiated in our system. No Payments / Refunds / Payouts
2 Success The transaction is successful. Yes Refunds / Payouts
3 Cancelled The payment was cancelled. The payments that can be cancelled are the payments with “Authorized” status or the payments that are cancelled by the customer on the form. Yes Payments
4 Failed The transaction has failed. Yes Payments / Refunds / Payouts
5 Expired The time period the customer had for completing the payment has expired. Yes Payments
7 PendingOnProvider The payment is awaiting approval from the downstream partners/acquirers. No Payments
9 Authorized The payment was successfully authorized. In the initial request the Capture parameter is sent to false so the responsibility of the capturing the payment is on the merchants side.
The goods can be delivered.
No Payments
11 Captured The transaction has been captured. Only payments with “Authorized” status can be captured.
The goods can be delivered.
Yes Payments
13 CaptureRequested The payment was successfully authorized and the capture request was also sent to the provider. In the initial request the capture parameter is sent to true so our service will handle the capturing of the payment automatically.
The goods can be delivered.
No Payments
14 Exception The transaction needs manual review from Smart2Pay. No Payments
15 CancelRequested The cancel request has been sent. No Payments
16 Reversed The authorization has been reversed (the money were credited back to the customer account). Yes Payments
19 Disputed The payment is disputed by the customer. No Payments
26 Chargedback The cardholder has won the dispute and has received the money back. Yes Payments
30 PendingChallengeConfirmation The fraud provider has challenged the payment. Payment is authorized. You can reject or accept the challenge. No Payments
33 QueuedForCapturing The payment will be sent automatically for capturing. No further action from you is required.
The goods can be delivered.
No Payments
34 QueuedForCanceling The payment will be sent automatically for canceling. No further action from you is required. No Payments
35 PartiallyCaptured The payment is partially captured. Yes Payments

Messages

In the Messages tab from the main menu you can see all your messages received or sent by you and you can send messages to our team concerning the different problems that you encounter.

Through the Messages tab we offer our own messaging framework from within the program, to improve and facilitate the communication between us and our business partners. It is very useful because it displays all your notifications, keeps a track of your messages and you can always see the history of conversations between certain users and our team. Its a simple system to use and understand, it saves time with automated responses but it also manages all the conversations in the Inbox tab.

4

When you access the Inbox tab, the search Filters section is collapsed. In order to expand it, just click on the Show filters. You can search messages depending on the sender and receiver. Once you enter the desired filters just click on the Filter 26 button.

4

Company Documents

After you have completed all the necessary details for the company profile, you need to wait for Smart2pay approval of the company.

The following message will appear when you will try to access the Company Documents tab:

4

After our team will review your company details and approve them, you will receive a confirmation message.

4

Once you access the Company Documents tab, you will see two sets of documents that that you need to provide in order for us to generate your DNA (Non Disclosure Agreement) and the Contract.

4

The documents that you need to provide us in order for us to generate your DNA (Non Disclosure Agreement), are the following: Company certificate / Incorporation certificate, Register of directors (or any other document showing individuals with signing rights), and the Passport copy of company owners. Once you upload the documents, you can click on the Submit Documents 26 button and wait for our team to review and approve the documents that you have sent.

4

If our team, while reviewing your documents, has agreed that you need to provide more information or the information is incomplete or outdated (like: expired passports or proof of address) they will reject your document.

4

You will also receive in Inbox a rejection message stating the reason of rejection.

4

After resolving the issues involved in the rejection of the document, you will have to delete first the document from the Company Documents tab and then you will have to upload the modified document.

4

You will also receive in Inbox a message stating which document has been deleted and the person who has deleted the document.

4

After our team will review and approve the documents that you have sent, you can generate your NDA document by using the Generate NDA 26 button.

4

For completing this step all parties involved need to sign the NDA.

4

The documents that you need to provide us in order for us to generate your Contract are the following: the Signed NDA, the Assigned package, and any kind of bill for each company owners or signing rights contacts which shows contact address. Once you upload the documents, you can click on the Submit Documents 26 button and wait for our team to review and approve the documents that you have sent.

4

Company

After the registration process is completed you will need to go to the Company tab in order to fill in the documentation requirements for customer and company, like: Company details and address, Company contacts, and also Company owners.

For completing the Company Details form, all the fields are mandatory and we encourage you to give us the necessary information with utmost consideration.

In the case that your business isn’t registered for VAT, in the EEC VAT Number filed you will click on the Not Applicable sign.

In order for us to understand and to know more about your business and services, please provide as much information about your products or services in the Business Model field.

If you have more than one website where you want to implement our services, you need to add each one of them by using the ADD SITE 26 button.

4

You will also need to provide the current headquarters address for your company, like: Street number, Postcode / Zipcode, City /State, Phone / Fax, and Country of establishment.

4

In order to complete the Contact Details form, you will have to enter the complete details by which a person can contact you, like: Contact Role, Legal Name, Email, Date of Birth and the complete address.

In the Contact Role field you will have to state the role that you have within the company. You will choose from one of the following roles: UBO (Owner), Director, Sales / Marketing, Billing, Developer, Support.

4

4

The Company Owners form must contain details of each company owner or/and company director that owns more than 25% of the company, like: their signing right (click only if the person has the right to sign all company contracts), Legal Name, Email, Date of Birth, and their complete address. In order to add a new company owner or/and a company director just use the ADD COMPANY OWNER 26 button and the ADD COMPANY DIRECTOR 26 button from the bottom of the page.

4

After you have completed all the necessary fields, just click on the Save Changes 26 button.

Registration Process

If you do not already have an account for Onboarding system you can click on “Register” link from http://s2pubuntu.cloudapp.net/onboarding/index.php?_route=index or browse the following URL: http://s2pubuntu.cloudapp.net/onboarding/index.php?_route=accounts-register

4

The registration process involves providing an Email and Password for accessing Onboarding dashboard.

After the registration is completed you will see a confirmation message: User account registered with success!

5

Please note that the account is not activated immediately after submitting the form. A notification email will be sent to you after the request is approved by Onboarding back-office operator.

All the fields are required; in case you do not complete all of them, you will get the message: Please fill out this field.

7

If you forgot the password just click the “Forgot your Password?” link. You will be required to provide your User Email.

Once you submit this form an email is sent automatically to you with a random generated password.

It is strongly recommended to change this password as soon as you login.

10

After you receive the email with the new password you can click the Login button and go to the login page.

Each user has the possibility to edit his profile and to change his password. To do this, you must access the login page and introduce the username and password in the required fields:

http://s2pubuntu.cloudapp.net/onboarding/index.php?_route=accounts-login

1

Online Boarding

Now that you tested our GlobalPay payment platform, you are ready to go live and use our product. Perfect! It will only take a little time for you to manage the onboarding process.

Onboarding is the tool that you need in order that the onboarding process to be quick and accurate and to ensure a long-term and successful business partnership.

We have strive to minimize the long and tiresome process during merchant boarding and the ongoing challenges of completing forms and fields while building the merchant’s and company’s profile. So we have developed an intuitive online system that it will allow merchants for an automated and quick onboarding process.

Settlement Cycles

In order to view and access the Invoicing tab you need to have assigned to your dashboard user account the proper access rights (Invoicing-view).

Smart2Pay is managing a complex schedule of settlements, and depending on the payment methods you are using, you can be settled in various cycles with various cutoffs.

By accessing the Invoicing tab->Settlement Cycles view, you can see important information on the invoicing/settlement cycles, invoice date, cutoffs and if any invoices are expected to be delayed. You have the possibility to search for specific cycle using different criteria.

84

Search filters

When you access the Invoicing tab->Settlement Cycles view, the Search Filters section is expanded. In order to collapse it just click the arrow on the right of the screen.

84

You can search invoices by using the following filters:

  • Invoice Type: Settlement Invoice – contains the fees and the payments; Settlement Report: contains only the payments; and Invoice: contains only the fees;
  • Invoice Cut Off: the time period for which the transactions will be invoiced;
  • Settlement Currency: the currency in which the settlement was made;
  • Site: the name of the merchant’s website in our financial system;
  • Method: the name of the payment method used and assigned for a specific settlement cycle;
  • Next Invoice Date: the date when the next invoice is to be generated;
  • On Hold: if set to no, invoices will be automatically generated and process by the system, if set to yes, it will be manually processed by our financial team when certain conditions are met.

WebMoney Transfer Test Data

For WebMoney Transfer payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

WebMoney Transfer via Moneta Payment Flow

  1. The customer selects his preferred currency from the list.

    1 Select currency

  2. The Customer selects the WebMoney option.

    1 Select payment option

  3. The Customer checks the details and proceeds with the payment by clicking on the Pay button.

    1 Check details

  4. The customer logs in to his WebMoney Transfer account by entering his login data (WMID, email address or phone number) and password.

    1 Account login

  5. The customer selects his purse/wallet (if he does not have a purse/wallet in the transaction currency one will be automatically created).

    The customer can confirm the payment:

    • by receiving a SMS on his registered phone number;
    • by receiving a code using the E-Num application installed in his mobile device.

    1 Payment confirmation option

  6. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Server to Server Card Payment

If you initiate a payment with the GenerateCreditCardToken element set to false, the token element is not sent in the response/notification, so you cannot used it for future payments, but the token is still created and associated with the credit card and the payment.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_i6",
    "Amount": 2000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "Card": {
      "HolderName": "John Doe",
      "Number": "4111111111111111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018",
      "SecurityCode": "312"
    },		
     "Capture": true,
     "Retry": true,
     "GenerateCreditCardToken": false
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202589,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20170511112434",
    "MerchantTransactionID": "s2ptest_i6",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "VISA-1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": null,
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": false
  }
}

Hosted Card Form

If you initiate a payment without any card or token details, you will be given in the response a RedirectURL, that will be used to redirect the customer to a form where he will have to fill all the necessary details and continue the payment.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h6",
    "Amount": 2000,
    "Currency": "EUR",	
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Capture": true
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202235,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205084804",
    "MerchantTransactionID": "s2ptest_h6",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 0,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": null,
    "StatementDescriptor": null,
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": 10,
    "Capture": true,
    "Retry": false,
    "RedirectURL": "https://securetest.smart2pay.com/v1/Payments/FillCardDetails?PaymentToken=202235.1010.A3F07F81639486814BAF3319CF96A9071",
    "3DSecure": null
  }
}

Also, if you initiate a Card payment using the CreditCardToken value without the SecurityCode parameter and with the RequireSecurityCode parameter set to true, a RedirectURL will be given in the response. Using this URL the customer will be redirected to a form where the card details are already filled, except the SecurityCode (card number is masked and cannot be changed). The customer will have to fill the value for the SecurityCode parameter and continue the payment.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_i9",
    "Amount": 2000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1",
      "RequireSecurityCode": true
    },		
     "Capture": true,
      "GenerateCreditCardToken": true
   }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202592,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20170511112846",
    "MerchantTransactionID": "s2ptest_i9",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": "0",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": null,
    "StatementDescriptor": null,
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "Ends with 1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1"
    },
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": 10,
    "Capture": true,
    "Retry": false,
    "RedirectURL": "https://securetest.smart2pay.com/v1/Payments/FillCardDetails?PaymentToken=202592.1010.8DBBBF0F45451A5D094F4CDD88E199698",
    "3DSecure": false
  }
}

One Click Payment

If you initiate a Card payment and you set the GenerateCreditCardToken parameter to true, a token element is sent in the response, containing the value of the newly created credit card token, that you can use for future payments.

The token received in the response, together with the Security Code (CVV) parameter or the RequireSecurityCode parameter, can be used to initiate future payments, without having to enter all the necesary card details again.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_i4",
    "Amount": 2000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1",
      "SecurityCode": "312"
    },		
     "Capture": true,
     "Retry": true,
     "GenerateCreditCardToken": true
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202587,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20170511111702",
    "MerchantTransactionID": "s2ptest_i4",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "Ends with 1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1"
    },
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": false
  }
}

For One Click Payments, you can decide whether the Security Code (CVV) is needed or not for the payments.

If you decide that the security code is not needed, you cand send the RequireSecurityCode parameter set to false. In this case, the client will not be redirected to the form page to fill in the security code, but the payment will be directly sent to the payment provider.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_i5",
    "Amount": 2000,
    "Currency": "EUR",
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1",
      "RequireSecurityCode": false 
    },		
     "Capture": true,
     "GenerateCreditCardToken": true
   }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202588,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20170511112248",
    "MerchantTransactionID": "s2ptest_i5",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": null,
    "Description": null,
    "StatementDescriptor": null,
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "Ends with 1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": {
      "Value": "F43F90A5CB613D91F704407D4E297EA1"
    },
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": false,
    "RedirectURL": null,
    "3DSecure": false
  }
}

Authorize Card Payment

Definition: POST /v1/payments

In order to initiate a Direct Card payment, you must create a payment object with the necessary card details.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h2",
    "Amount": 2000,
    "Currency": "EUR",
    "Card": {
      "HolderName": "John Doe",
      "Number": "4111111111111111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018",
      "SecurityCode": "312"
    },		
     "Capture": true
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202230,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205084103",
    "MerchantTransactionID": "s2ptest_h2",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": null,
    "Description": null,
    "StatementDescriptor": null,
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "VISA-1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": null,
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": false,
    "RedirectURL": null,
    "3DSecure": null
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

Also, when the validation fails, an invalid request is inserted in the database and the ID of the newly inserted invalid request is sent in the Payment response. The value of the element InvalidRequestID is prefixed with ”i” to not be confused with the Payment ID.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h2",
    "Amount": 2000,
    "Currency": "EUR",
    "Card": {
      "HolderName": "John Doe",
      "Number": "4111111111111111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018",
      "SecurityCode": "312"
    },		
     "Capture": true
  }
}

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "InvalidRequestID": "i3065",
    "ID": null,
    "ClientIP": null,
    "SkinID": null,
    "Created": null,
    "MerchantTransactionID": "s2ptest_h2",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 0,
    "ReturnURL": null,
    "Description": null,
    "StatementDescriptor": null,
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "Ends with 1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": null,
    "Status": {
      "ID": null,
      "Info": null,
      "Reasons": [
        {
          "Code": "20",
          "Info": "Key is duplicated"
        }
      ]
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": false,
    "RedirectURL": null,
    "3DSecure": null
  }
}

See our section: Create a Complex Direct Card Payment for a complete example of a direct card payment.

Via Baloto Test Data

For Via Baloto payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Via Baloto Payment Flow

  1. The customer enters his email address.

    1 Enter email

  2. The customer selects his preferred payment method from the list.

    1 Select payment method

  3. The customer receives the payment instructions and clicks on the Generate Invoice button.

    1 Generate invoice

  4. The customer receives the payment receipt containing the payment details. He needs to print the receipt and pay it at any branch of Via Baloto in the country.

    1 Payment receipt

PSE Test Data

For PSE payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

PSE Payment Flow

  1. The customer enters his email address.

    1 Enter email

  2. After selecting the payment method, the customer enters the required information and proceeds with the payment using the Pay button.

    1 Payment details

  3. The customer enters his email address registered in PSE and completes the payment.

    1 Payment confirmation

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

WebMoney Transfer Test Data

For WebMoney Transfer payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

WebMoney Transfer Payment Flow

  1. The customer chooses his preferred currency from the list and enters his email address.

    1 Enter email

  2. The customer logs in to his WebMoney Transfer account by entering his login data (WMID, email address or phone number) and password.

    1 Account login

  3. The customer selects one WMID from the list and continues the payment.

    1 Select WMID

  4. The customer selects his purse/wallet (if he does not have a purse/wallet in the transaction currency one will be automatically created).

    The customer can confirm the payment:

    • by receiving a SMS on his registered phone number
    • by receiving a code using the E-Num application installed in his mobile device.

    1 Payment confirmation option

  5. Using his E-Num application the customer scans the QR-code and enters the response code received, in order to confirm the payment.

    1 Payment confirmation

  6. The customer verifies the transaction details and he also has the possibility to print them.

    1 Transaction details

  7. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Alipay Test Data

For Alipay payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Alipay Payment Flow

  1. The Customer selects his preferred currency from the list and continues the payment.

    1 Select currency

  2. Once the customer arrives at the provider’s page he has two choices: to continue with the payment using the mobile version or using the desktop version.

    1 Payment version

  3. The customer logs in to his Alipay account by entering his email address and password.

    1 Account login

  4. The customer confirms the payment by entering the payment password.

    1 Payment password

  5. The payment is processing.

    1 Payment processing

  6. In a few seconds the customer will be redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Get a list of payouts (filtered)

You can specify various filters as parameters in the query string in order to get a customized list of payouts.

Requests:

GET https://securetest.smart2pay.com/v1/payouts?limit=3
Authorization: Basic MTAxMDpnYWJp
GET https://securetest.smart2pay.com/v1/payouts?maximumAmount=1000
Authorization: Basic MTAxMDpnYWJp

The following table describes the possible filters you can use. You can mix the filters so you can obtain the desired results.

FILTERS
Field Description Data type
limit The maximum number of items that will be returned Long
offset A list of payments starting with the value of the offset parameter will be returned. The offset parameter can also be used together with the limit parameter to select specific entries within a list of payments. String
startDate The date and time after which the payments are returned DateTime

(YYYYMMDDHHMMSS)

endDate The date and time until which the payments are returned DateTime

(YYYYMMDDHHMMSS)

country Only the transactions having this country code will be returned String

(ISO 3166-1-alpha-2)

currency Only the transactions having this currency code will be returned String

(ISO 4217)

minimumAmount Only the payments with an amount higher than this will be returned Integer (last 2 digits representing the decimal part)
maximumAmount Only the payments with an amount lower than this will be returned Integer (last 2 digits representing the decimal part)
merchantTransactionID Only the payment having this merchantTransactionID will be returned String

^[0-9a-zA-Z_-]{1,50}$

statusID Only the transactions having this statusID will be returned. Integer

The ID of the payment status can have the following values: 1 – Open, 2 – Success, 3 – Cancelled, 4 – Failed, 5 – Expired, 9 – Authorized.

methodTransactionID Only the payments having this methodTransactionID will be returned. This transaction ID from the payment method provider can be used for customer support. String

^[0-9a-zA-Z_-]{1,50}$

Here is an example of a request with the limit filter set to 3. This means that it will only return 3 transactions in a descending order.

Request:

GET https://securetest.smart2pay.com/v1/payouts?limit=3
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payouts": [
    {
      "ID": 79,
      "SiteID": 1010,
      "Created": "20161003095713",
      "MerchantTransactionID": "test_g23",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 78,
      "SiteID": 1010,
      "Created": "20161003095708",
      "MerchantTransactionID": "test_g22",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 77,
      "SiteID": 1010,
      "Created": "20161003095114",
      "MerchantTransactionID": "test_g20",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    }
  ]
}

You can also mix various filters to get specific results. Here is an example of a request with the limit filter set to 2 and the currency EUR. This means that it will return the last two payout entries that have the transaction currency EUR.

Request:

GET https://securetest.smart2pay.com/v1/payouts?limit=2&currency=EUR
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payouts": [
    {
      "ID": 79,
      "SiteID": 1010,
      "Created": "20161003095713",
      "MerchantTransactionID": "test_g23",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 78,
      "SiteID": 1010,
      "Created": "20161003095708",
      "MerchantTransactionID": "test_g22",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    }
  ]
}

Get a list of direct card payments (filtered)

You can specify various filters as parameters in the query string in order to get a customized list of direct card payments.

Requests:

GET https://securetest.smart2pay.com/v1/payments?limit=2
Authorization: Basic MTAxMDpnYWJp
GET https://securetest.smart2pay.com/v1/payments?startDate=20160803150000&endDate=20161003140000
Authorization: Basic MTAxMDpnYWJp

The following table describes the possible filters you can use. You can mix the filters so you can obtain the desired results.

FILTERS
FieldDescriptionData type
limitThe maximum number of items that will be returnedLong
offsetA list of payments starting with the value of the offset parameter will be returned. The offset parameter can also be used together with the limit parameter to select specific entries within a list of payments.String
startDateThe date and time after which the payments are returnedDateTime (YYYYMMDDHHMMSS)
endDateThe date and time until which the payments are returnedDateTime (YYYYMMDDHHMMSS)
countryOnly the transactions having this country code will be returnedString (ISO 3166-1-alpha-2)
currencyOnly the transactions having this currency code will be returnedString (ISO 4217)
minimumAmountOnly the payments with an amount higher than this will be returnedInteger (last 2 digits representing the decimal part)
maximumAmountOnly the payments with an amount lower than this will be returnedInteger (last 2 digits representing the decimal part)
merchantTransactionIDOnly the payment having this merchantTransactionID will be returnedString

^[0-9a-zA-Z_-]{1,50}$

statusIDOnly the transactions having this statusID will be returned.Integer

The ID of the payment status can have the following values: 1 – Open, 3 – Cancelled, 4 – Failed, 5 – Expired, 9 – Authorized, 11 – Captured.

methodTransactionIDOnly the payments having this methodTransactionID will be returned. This transaction ID from the payment method provider can be used for customer support.String

^[0-9a-zA-Z_-]{1,50}$

Here is an example of a request with the currency filter set to EUR. This means that it will return only the transactions with this payment currency.

Request:

GET https://securetest.smart2pay.com/v1/payments?limit=2
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payments": [
    {
      "ID": 202245,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205094557",
      "MerchantTransactionID": "s2ptest_h17",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 2000,
      "ReturnURL": null,
      "Description": null,
      "StatementDescriptor": null,
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 11,
        "Info": "Captured",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    },
    {
      "ID": 202244,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205094546",
      "MerchantTransactionID": "s2ptest_h16",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 0,
      "ReturnURL": null,
      "Description": null,
      "StatementDescriptor": null,
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 9,
        "Info": "Authorized",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    }
  ]
}

Get a list of payouts

Without specifying any parameters a list of payouts is returned. Please be aware that only a limited amount of details for each payout will be provided.

Definition: GET /v1/payouts

Request:

GET https://securetest.smart2pay.com/v1/payouts
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payouts": [
    {
      "ID": 77,
      "SiteID": 1010,
      "Created": "20161003095114",
      "MerchantTransactionID": "test_g20",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 75,
      "SiteID": 1010,
      "Created": "20161003092652",
      "MerchantTransactionID": "test_g18",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 74,
      "SiteID": 1010,
      "Created": "20161003092615",
      "MerchantTransactionID": "test_g17",
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 66,
      "SiteID": 1010,
      "Created": "20160602115128",
      "MerchantTransactionID": "test_e37",
      "Amount": 2000,
      "Currency": "EUR",
      "Description": "payment product",
      "StatementDescriptor": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    }
  ]
}

Get a list of refunds of a specific direct card payment

You can get a list of refunds for a specific direct card payment by using an action based on GET HTTP request. Please be aware that only a limited amount of details for each refund will be provided.

Definition: GET /v1/payments/{id}/refunds/

Where:
  • {id} – GlobalPay Payment ID

Request:

GET https://securetest.smart2pay.com/v1/payments/202247/refunds
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Refunds": [
    {
      "ID": 266,
      "SiteID": 1010,
      "Created": "20161205095522",
      "MerchantTransactionID": "s2ptest_h22",
      "OriginatorTransactionID": null,
      "InitialPaymentID": 202247,
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "refund reason",
      "StatementDescriptor": null,
      "Customer": null,
      "BillingAddress": null,
      "BankAddress": null,
      "Articles": null,
      "Status": {
        "ID": 4,
        "Info": "Failed",
        "Reasons": [
          {
            "Code": "2206",
            "Info": "Refund.Amount exceeds initial payment available amount"
          }
        ]
      }
    },
    {
      "ID": 265,
      "SiteID": 1010,
      "Created": "20161205095515",
      "MerchantTransactionID": "s2ptest_h21",
      "OriginatorTransactionID": null,
      "InitialPaymentID": 202247,
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "refund reason",
      "StatementDescriptor": null,
      "Customer": null,
      "BillingAddress": null,
      "BankAddress": null,
      "Articles": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    },
    {
      "ID": 264,
      "SiteID": 1010,
      "Created": "20161205095505",
      "MerchantTransactionID": "s2ptest_h20",
      "OriginatorTransactionID": null,
      "InitialPaymentID": 202247,
      "Amount": 1000,
      "Currency": "EUR",
      "Description": "refund reason",
      "StatementDescriptor": null,
      "Customer": null,
      "BillingAddress": null,
      "BankAddress": null,
      "Articles": null,
      "Status": {
        "ID": 2,
        "Info": "Success",
        "Reasons": []
      }
    }
  ]
}

Get a list of direct card payments

Without specifying any parameters a list of direct card payments is returned. Please be aware that only a limited amount of details for each direct card payment will be provided.

Definition: GET /v1/payments

Request:

GET https://securetest.smart2pay.com/v1/payments
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payments": [
    {
      "ID": 202245,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205094557",
      "MerchantTransactionID": "s2ptest_h17",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 2000,
      "ReturnURL": null,
      "Description": null,
      "StatementDescriptor": null,
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 11,
        "Info": "Captured",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    },
    {
      "ID": 202244,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205094546",
      "MerchantTransactionID": "s2ptest_h16",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 0,
      "ReturnURL": null,
      "Description": null,
      "StatementDescriptor": null,
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 9,
        "Info": "Authorized",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    },
    {
      "ID": 202243,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205093245",
      "MerchantTransactionID": "s2ptest_h13",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 0,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "payment product",
      "StatementDescriptor": "bank statement message",
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": {
        "ID": 115,
        "MerchantCustomerID": "null",
        "Email": "customer@test.com",
        "FirstName": "John",
        "LastName": "Doe",
        "Gender": "1",
        "SocialSecurityNumber": "45908-28324",
        "Phone": "0744-783322",
        "Company": "S2P"
      },
      "BillingAddress": {
        "ID": 253,
        "City": "Iasi",
        "ZipCode": "7000-49",
        "State": "Iasi",
        "Street": "Sf Lazar",
        "StreetNumber": "37",
        "HouseNumber": "5A",
        "HouseExtension": "-",
        "Country": "RO"
      },
      "ShippingAddress": {
        "ID": 87,
        "City": "Iasi",
        "ZipCode": "700049",
        "State": "Iasi",
        "Street": "Sf Lazar",
        "StreetNumber": "37",
        "HouseNumber": "-",
        "HouseExtension": "-",
        "Country": "RO"
      },
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 1,
        "Info": "Open",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    },
    {
      "ID": 202242,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205093117",
      "MerchantTransactionID": "s2ptest_h12",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 2000,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "payment product",
      "StatementDescriptor": "bank statement message",
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": {
        "ID": 115,
        "MerchantCustomerID": "null",
        "Email": "customer@test.com",
        "FirstName": "John",
        "LastName": "Doe",
        "Gender": "1",
        "SocialSecurityNumber": "45908-28324",
        "Phone": "0744-783322",
        "Company": "S2P"
      },
      "BillingAddress": {
        "ID": 253,
        "City": "Iasi",
        "ZipCode": "7000-49",
        "State": "Iasi",
        "Street": "Sf Lazar",
        "StreetNumber": "37",
        "HouseNumber": "5A",
        "HouseExtension": "-",
        "Country": "RO"
      },
      "ShippingAddress": {
        "ID": 87,
        "City": "Iasi",
        "ZipCode": "700049",
        "State": "Iasi",
        "Street": "Sf Lazar",
        "StreetNumber": "37",
        "HouseNumber": "-",
        "HouseExtension": "-",
        "Country": "RO"
      },
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 11,
        "Info": "Captured",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    },
    {
      "ID": 202240,
      "ClientIP": null,
      "SkinID": null,
      "Created": "20161205092303",
      "MerchantTransactionID": "s2ptest_h11",
      "OriginatorTransactionID": null,
      "Amount": 2000,
      "Currency": "EUR",
      "CapturedAmount": 1000,
      "ReturnURL": null,
      "Description": null,
      "StatementDescriptor": null,
      "MethodID": 6,
      "MethodOptionID": null,
      "SiteID": 1010,
      "NotificationDateTime": null,
      "Customer": null,
      "BillingAddress": null,
      "ShippingAddress": null,
      "Articles": null,
      "Card": null,
      "CreditCardToken": null,
      "Status": {
        "ID": 35,
        "Info": "PartiallyCaptured",
        "Reasons": []
      },
      "MethodTransactionID": null,
      "PaymentTokenLifetime": null,
      "Capture": null,
      "Retry": null,
      "RedirectURL": null,
      "3DSecure": null
    }
  ]
}

Get information on a specific refund for a direct payment

You can get information about a refund by using the following action based on Get HTTP request.

Definition: GET /v1/payments/{id}/refunds/{id}

Where:
  • payments/{id} – GlobalPay Payment ID
  • and
  • refunds/{id} – GlobalPay Refund ID

Request:

GET https://securetest.smart2pay.com/v1/payments/202246/refunds/263
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8



{
  "Refund": {
    "ID": 263,
    "SiteID": 1010,
    "Created": "20161205095348",
    "MerchantTransactionID": "s2ptest_h19",
    "OriginatorTransactionID": null,
    "InitialPaymentID": 0,
    "Amount": 2000,
    "Currency": "EUR",
    "Description": "refund reason",
    "StatementDescriptor": null,
    "Customer": null,
    "BillingAddress": null,
    "BankAddress": null,
    "Articles": null,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": []
    }
  }
}

Create a Refund for a Direct Card Payment

You can initiate refunds only for transactions with a Captured payment status. When you are initiating a refund you need to provide the Refund Amount and the Merchant Transaction ID, that is automatically generated. You can change this ID by introducing your ID value.

The refunds can be full and/or partial depending if you have to return all the money to customer or not.

Full refund means you can only refund the entire captured amount for the initial transaction.

Partial refund means you have the possibility to refund a smaller amount than the one from the initial captured transaction. You can perform more than one refund for a transaction with the limitation that the sum of partial refunds to be smaller or equal than the initial captured amount.

Definition: POST /v1/payments/{id}/refunds

Where:
  • {id} – GlobalPay Payment ID

A 200 HTTP response (OK) is returned if the request was completed successfully.

Request:

POST https://securetest.smart2pay.com/v1/payments/202246/refunds
Authorization: Basic MTAxMDpnYWJp

{
 "Refund": {
   "MerchantTransactionID": "s2ptest_h19",
   "OriginatorTransactionID": "108_a",
   "Amount": 2000,   
   "Description": "refund reason"
  }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8



{
  "Refund": {
    "ID": 263,
    "SiteID": 1010,
    "Created": "20161205095348",
    "MerchantTransactionID": "s2ptest_h19",
    "OriginatorTransactionID": "108_a",
    "InitialPaymentID": 0,
    "Amount": 2000,
    "Currency": "EUR",
    "Description": "refund reason",
    "StatementDescriptor": null,
    "Customer": null,
    "BillingAddress": null,
    "BankAddress": null,
    "Articles": null,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": []
    }
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://securetest.smart2pay.com/v1/payments/202247/refunds
Authorization: Basic MTAxMDpnYWJp

{
 "Refund": {
   "MerchantTransactionID": "s2ptest_h22",
   "OriginatorTransactionID": "109_a",
   "Amount": 1000,   
   "Description": "refund reason"
  }
}

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Refund": {
    "ID": 266,
    "SiteID": 1010,
    "Created": "20161205095522",
    "MerchantTransactionID": "s2ptest_h22",
    "OriginatorTransactionID": "109_a",
    "InitialPaymentID": 0,
    "Amount": 1000,
    "Currency": "EUR",
    "Description": "refund reason",
    "StatementDescriptor": null,
    "Customer": null,
    "BillingAddress": null,
    "BankAddress": null,
    "Articles": null,
    "Status": {
      "ID": 4,
      "Info": "Failed",
      "Reasons": [
        {
          "Code": "2206",
          "Info": "Refund.Amount exceeds initial payment available amount"
        }
      ]
    }
  }
}

Get information on a specific payout

You can get information about a payout by using GET HTTP request.

Definition: GET /v1/payouts/{id}

Where:
  • {id} – GlobalPay Payout ID

Request:

GET https://securetest.smart2pay.com/v1/payouts/77
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payout": {
    "ID": 77,
    "SiteID": 1010,
    "Created": "20161003095114",
    "MerchantTransactionID": "test_g20",
    "Amount": 1000,
    "Currency": "EUR",
    "Description": "payment product",
    "StatementDescriptor": null,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": []
    }
  }
}

Get the status of a payout

You can get the status of a payout by using the following GET HTTP request.

Please note that this method sends only the status information about a payout. To receive more information about a payout please go to our section Get information on a specific payout.

Definition: GET /v1/payouts/{id}/status

Where:
  • {id} – GlobalPay Payout ID

Request:

GET https://securetest.smart2pay.com/v1/payouts/77/status
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payout": {
    "ID": 77,
    "MerchantTransactionID": "test_g20",
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": []
    }
  }
}

Create a payout

Definition: POST /v1/payouts

In order to initiate a payout, you must create a payment object with all the necessary card details.

Request:

POST https://securetest.smart2pay.com/v1/payouts
Authorization: Basic MTAxMDpnYWJp

{
 "Payout": {
  "MerchantTransactionID": "test_g20",
  "Amount": 1000,
  "Currency": "EUR",
  "Description": "payment product",
  "Card": {
   "HolderName": "John Doe",
   "Number": "4111111111111111",
   "ExpirationMonth": "02",
   "ExpirationYear": "2019"
   }
 }
}

Response:

HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8

{
  "Payout": {
    "ID": 77,
    "SiteID": 1010,
    "Created": "20161003095114",
    "MerchantTransactionID": "test_g20",
    "Amount": 1000,
    "Currency": "EUR",
    "Description": "payment product",
    "StatementDescriptor": null,
    "Status": {
      "ID": 2,
      "Info": "Success",
      "Reasons": []
    }
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://securetest.smart2pay.com/v1/payouts
Authorization: Basic MTAxMDpnYWJp

{
 "Payout": {
  "MerchantTransactionID": "test_g21",
  "Amount": 1000,
  "Currency": "EUR",
  "Description": "payment product"
 }
}

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Payout": {
    "InvalidRequestID": "i1703",
    "ID": null,
    "SiteID": 1010,
    "Created": null,
    "MerchantTransactionID": "test_g21",
    "Amount": 1000,
    "Currency": "EUR",
    "Description": "payment product",
    "StatementDescriptor": null,
    "Status": {
      "ID": null,
      "Info": null,
      "Reasons": [
        {
          "Code": "1206",
          "Info": "CardDetails are missing"
        }
      ]
    }
  }
}

Direct Card Payment Notification Format

We will notify you about the new status of the payment to the Notification URL you setup in the Merchant Dashboard.

You need to respond with HTTP code 204 (No Content)!

Payment notification format:

Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "ID": 202242,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205093117",
    "MerchantTransactionID": "s2ptest_h12",
    "OriginatorTransactionID": "100_a",
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": {
      "HolderName": "John Doe",
      "Number": "VISA-1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": {
      "Value": "6BEBF42B0E43D3BFD360DFB5EFF9D96D"
    },
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

Response:

204 No Content

Capture a Card Payment

Definition: POST /v1/payments/{id}/capture

Where:
  • {id} – GlobalPay Payment ID

A payment can only be captured if it has an Authorized status. The Authorized status can only be obtained for direct card payments initiated with Capture parameter set to false.

Once the payment has an Authorized status, you can capture either a partial amount or the full amount of the initial authorized amount for the transaction.

Full capture means you capture the entire authorized amount for the initial transaction.

A 200 HTTP response (OK) is returned if the request was completed successfully.

Request:

POST https://securetest.smart2pay.com/v1/payments/202238/capture
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202238,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205091735",
    "MerchantTransactionID": "s2ptest_h9",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": false,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

Partial capture means you have the possibility to capture a smaller amount than the one from the initial authorized transaction.

You can perform only one partial capture for an authorized transaction with the limitation that the amount of the partial capture to be smaller or equal than the initial authorized amount.

You need to specify the captured amount parameter in the query string, in order to partially capture a payment.

Request:

POST https://securetest.smart2pay.com/v1/payments/202239/capture?amount=1000
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202239,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205091934",
    "MerchantTransactionID": "s2ptest_h10",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 1000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 35,
      "Info": "PartiallyCaptured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": false,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://securetest.smart2pay.com/v1/payments/202238/capture
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202238,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205091735",
    "MerchantTransactionID": "s2ptest_h9",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 2000,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": [
        {
          "Code": "1006",
          "Info": "Payment.State is invalid"
        }
      ]
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": false,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

Cancel a Card Payment

Definition: POST /v1/payments/{id}/cancel

Where:
  • {id} – GlobalPay Payment ID

A payment can be cancelled if it has an Authorized status. The Authorized status can only be obtained for direct card payments initiated with Capture parameter set to false.

A 200 HTTP response (OK) is returned if the request was completed successfully.

Request:

POST https://securetest.smart2pay.com/v1/payments/202237/cancel
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
  "Payment": {
    "ID": 202237,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205091456",
    "MerchantTransactionID": "s2ptest_h8",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 0,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 3,
      "Info": "Cancelled",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": false,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

In case of an API error, an HTTP 4xx (you did something wrong) or HTTP 5xx (we did something wrong) response is returned.

For more information about the reasons of a wrong request response see our section GlobalPay Return Codes.

Request:

POST https://securetest.smart2pay.com/v1/payments/202237/cancel
Authorization: Basic MTAxMDpnYWJp

Response:

HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8\

{
  "Payment": {
    "ID": 202237,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205091456",
    "MerchantTransactionID": "s2ptest_h8",
    "OriginatorTransactionID": null,
    "Amount": 2000,
    "Currency": "EUR",
    "CapturedAmount": 0,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "MethodID": 6,
    "MethodOptionID": null,
    "SiteID": 1010,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 115,
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "BillingAddress": {
      "ID": 253,
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "ID": 87,
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 3,
      "Info": "Cancelled",
      "Reasons": [
        {
          "Code": "1006",
          "Info": "Payment.State is invalid"
        }
      ]
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": false,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

PayPal Test Data

For PayPal payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

PayPal Payment Flow

  1. The Customer selects his preferred currency from the list and enters his email address.

    1 Enter email

  2. The Customer sees the payment details and continues the payment.

    1 Payment details

  3. The customer logs in to his PayPal account by entering his email address and password.

    1 Account login

  4. The Customer reviews the payment information and confirms the payment.

    1 Payment details

  5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Referenced Payment Test Data

For Referenced Payment payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Referenced Payment Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer selects his preferred payment method from the list.

    1 Select payment method

  3. The customer receives a voucher containing the payment details and a barcode. He needs to print the voucher with the barcode and pay it at any branch of Bancolombia or Banco de Occidente in the country.

    1 Print voucher

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

ACH Debit Test Data

For ACH Debit payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

ACH Debit Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer selects his preferred payment method from the list.

    1 Select payment method

  3. After selecting the payment method, the customer enters the required information and proceeds with the payment.

    1 Login details

  4. The customer receives a message that the payment was successfully processed. He also has the possibility to print the transaction details.

    1 Payment confirmation

  5. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

Débito Banco do Brasil Test Data

For Débito Banco do Brasil payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Débito Banco do Brasil Payment Flow

  1. The Customer enters his name and email address.

    1 Enter name and email

  2. The Customer chooses his account type.

    1 Account type selection

  3. The customer logs in to his account by entering the login details and authorizes the payment.

    1 Account login

  4. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Transferência entre Contas Test Data

For Transferência entre Contas Bradesco payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Transferência entre Contas Bradesco Payment Flow

  1. The customer enters his name and email address.

    1 Enter name and email

  2. The customer enters the details required for the transfer.

    1 Enter details

  3. The customer enters his signature.

    1 Enter signature

  4. The customer enters the key in his security device.

    1 Enter key

  5. The customer chooses his account.

    1 Select account

  6. The customer authorizes the payment with a new key.

    1 Payment authorization

  7. The customer receives the payment confirmation.

    1 Payment confirmation received

Yandex Test Data

For Yandex payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Yandex Payment Flow

  1. The customer chooses the payment currency from the list.

    1 Select currency

  2. The Customer logs in to his Yandex.Money account with his username and password.

    1 Login details

  3. The customer sees the payment summary and he confirms the payment by introducing the payment password.

    1 Confirm transaction

  4. The customer receives the payment confirmation.

    1 Payment confirmation

  5. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Sberbank SMS/Online Test Data

For Sberbank SMS/Online payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Sberbank SMS/Online Payment Flow

  1. The customer enters his email address.

    1 Enter email

  2. The customer is redirected to Sberbank payment page where he has two options to pay: by text message or through Sberbank Online.

    If the customer chooses to pay by text message confirmation he will fill the phone number.

    1 Enter phone number

  3. The customer will receive a text message to which he needs to reply with a code to confirm the payment.

    1 Request sent

  4. The text message with the code to confirm the payment.

    1 Payment confirmation

  5. If the customer chooses to pay through Sberbank Online he will select the option and fill his phone number.

    1 Enter phone number

  6. The customer logs as usual into his Sberbank online account where he selects the card to be used.

    1 Login details

  7. The customer reviews the payment details and confirms the payment by sms password. He can also use a password printed on a receipt at any Sberbank ATM or terminal.

    1 Payment details

  8. The customer can also use a password printed on a receipt at any Sberbank ATM or terminal.

    1 Payment confirmation

  9. The customer receives a sms with a password for confirmation of the transaction.

    1 Sms password

  10. Complete the payment by using the received password.

    1 Payment confirmation

  11. The payment is confirmed.

    1 Payment confirmation received

Danamon Online Banking Test Data

For Danamon Online Banking payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Danamon Online Banking Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The payment details are displayed and the customer can proceed with the payment on Danamon Online Banking page.

    1 Payment details

  3. The customer logs in to his account with his User ID and password and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Mandiri ATM Automatic Test Data

For Mandiri ATM Automatic payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Mandiri ATM Automatic Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives a reference number and a virtual account that he will use to make the payment at an ATM.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

Indosat Dompetku Test Data

For Indosat Dompetku payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Indosat Dompetku Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer enters his phone number then confirms the payment with his mobile phone.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

T-Cash Test Data

For T-Cash payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

T-Cash Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives the details of the payment and proceeds to pay with T-Cash.

    1 Payment details

  3. The customer confirms the payment using a TCash token.

    1 Payment confirmation

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

IB Muamalat Test Data

For IB Muamalat payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

IB Muamalat Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives the details of the payment and proceeds to pay with IB Muamalat.

    1 Payment details

  3. The customer logs in to his account with his User ID and password and makes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

EPS Test Data

In order for you to test EPS payment method successfully, please use the below test data.

EPS Test Data
Data Value
BIC HYPTAT22XXX
Verfügernummer 123456
Verfügername Enter any name (example: John) or leave it empty, and click Login
PIN Enter any number (example: 123) or leave it empty, and click Login
Mobile TAN Enter any number (example: 1234) or leave it empty, and click OK

EPS Payment Flow

  1. The Customer enters the BIC and selects his preferred bank. The test BIC is: HYPTAT22XXX.

    1 Select bank

  2. The customer enters his login details. For test purposes you don’t need to enter any data (name or PIN), just click on the Login Button.

    1 Login details

  3. The customer reviews the payment details and proceeds with the payment.

    1 Review details

  4. The customer chooses to confirm the payment using mobile TAN.

    1 Mobile TAN

  5. The customer confirms the payment by using the TAN number.

    1 Payment confirmation

  6. The customer receives a message that the EPS online transfer was successful.

    1 Payment confirmation received

  7. Upon completion of the payment flow the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Mandiri e-Cash Test Data

For Mandiri e-Cash payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Mandiri e-Cash Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives the details of the payment and proceeds to pay with Mandiri e-Cash.

    1 Payment details

  3. The customer logs in to his account by entering his phone number and PIN and makes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

CIMB Clicks Test Data

For CIMB Clicks payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

CIMB Clicks Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives the details of the payment and proceeds to pay with CIMB Clicks.

    1 Payment details

  3. The customer logs in to his account by entering his User ID and makes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Kartuku Test Data

For Kartuku payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Kartuku Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives an email with the reference number and the virtual account which he uses to make the payment at an ATM.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

BII VA Test Data

For BII VA payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

BII VA Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer receives a reference number and a virtual account that he uses to make the payment at an ATM.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is Processing

Credit Card Test Data

For Credit Card (Indonesia) payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Credit Card Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer enters his card details (Cardholder Name, Credit card No, CVC/CVV2, Expiry Date, Card Issuing Country, Card Issuing Bank) and finalizes the payment.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

XL Tunai Test Data

For XL Tunai payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

XL Tunai Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details and the payment instructions.

    1 Payment details

Mandiri Clicks Test Data

For Mandiri Clicks payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Mandiri Clicks Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer enters his card number and the generated token number to finalize the payment.

    1 Payment details

  3. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Webcash Test Data

For Webcash payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Webcash Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Webcash.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

RHB Test Data

For RHB payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

RHB Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with RHB.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Mybank2U Test Data

For Mybank2U payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Mybank2U Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Mybank2U.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

Hong Leong Bank Transfer Test Data

For Hong Leong Bank Transfer payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

Hong Leong Bank Transfer Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with Hong Leong Bank Transfer.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

FPX Test Data

For FPX payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

FPX Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with FPX.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

CIMB Clicks Test Data

For CIMB Clicks payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

CIMB Clicks Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with CIMB Clicks.

    1 Payment details

  3. The customer logs in to his account by entering his User ID and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

AmBank Test Data

For AmBank payment method there aren’t any test data available, but you can see how it works with the payment flow given below.

AmBank Payment Flow

  1. The customer enters his email address, name and phone number.

    1 Customer details

  2. The customer is shown the details of his payment and proceeds to pay with AmBank.

    1 Payment details

  3. The customer logs in to his account and completes the payment.

    1 Account login

  4. Upon completion of the payment flow, the customer is redirected back to your ReturnURL.

    1 Return page when the redirection status is a success

IXE Pago referenciado Test Data

In order for you to test IXE Pago referenciado payment method successfully, you don’t need any given test data.

IXE Pago referenciado Payment Flow

  1. The customer enters the r