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": 1721,
      "Created": "20160902112825",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_f12",
      "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
    },
    {
      "ID": 1539,
      "Created": "20160718125803",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_12a",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 2,
        "Info": "Open",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 1495,
      "Created": "20160708074534",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_DIFUSION",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 2,
        "Info": "Open",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 1299,
      "Created": "20160314131438",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "s2ptest_41",
      "RecurringPeriod": 0,
      "PreapprovedMaximumAmount": null,
      "Currency": null,
      "ReturnURL": "http://demo.smart2pay.com/redirect.php",
      "Description": "1 year subscription",
      "Customer": null,
      "BillingAddress": null,
      "Status": {
        "ID": 1,
        "Info": "Pending",
        "Reasons": null
      },
      "RedirectURL": null,
      "MethodOptionID": 0
    },
    {
      "ID": 1016,
      "Created": "20151001120305",
      "MethodID": 46,
      "SiteID": 30201,
      "MerchantPreapprovalID": "101010",
      "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”.

Direct Card 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 Direct 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 Direct 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
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, 2 – Success, 3 – Cancelled, 4 – Failed, 5 – Expired, 9 – Authorized.

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 minimumAmount filter set to 2000. This means that it will return only the transactions with an amount higher than this.

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 required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives the payment instructions. In order to complete the payment, he needs to print the instructions and go to a physical bank branch in his area and pay with cash or check deposit.

    1 Payment instructions

Oxxo Pago en efectivo Test Data

In order for you to test Oxxo Pago en efectivo payment method successfully, you don’t need any given test data.

Oxxo Pago en efectivo Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives a voucher with a barcode. In order to complete the payment, he needs to print the voucher with the barcode and pay it at any Oxxo store.

    1 Payment instructions

7-Eleven Pago en efectivo Test Data

In order for you to test 7-Eleven Pago en efectivo payment method successfully, you don’t need any given test data.

7-Eleven Pago en efectivo Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives a voucher with a barcode. In order to complete the payment, he needs to print the voucher with the barcode and pay it at any 7-Eleven store.

    1 Payment instructions

ScotiaBank Pago referenciado Test Data

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

ScotiaBank Pago referenciado Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives the payment instructions. In order to complete the payment, he needs to print the instructions and go to a physical bank branch in his area and pay with cash or check deposit.

    1 Payment instructions

Santander Pago referenciado Test Data

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

Santander Pago referenciado Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives the payment instructions. In order to complete the payment, he needs to print the instructions and go to a physical bank branch in his area and pay with cash or check deposit.

    1 Payment instructions

Bancomer Pago referenciado Test Data

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

Bancomer Pago referenciado Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives the payment instructions. In order to complete the payment, he needs to print the instructions and go to a physical bank branch in his area and pay with cash or check deposit.

    1 Payment instructions

Boleto Itaú Test Data

In order for you to test Boleto Itaú payment method successfully, you don’t need any given test data.

Boleto Itaú Payment Flow

  1. The customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The customer receives the Boleto with all the necessary payment details. In order to complete the payment, he needs to print the Boleto and go to a physical bank branch in his area and pay with cash, use online banking, or simply go to an ATM machine.

    1 Print Boleto

Pagos en efectivo Test Data

In order for you to test Pagos en efectivo (Argentina) payment method successfully, you don’t need any given test data.

Pagos en efectivo Payment Flow

  1. The Customer enters the required details: email address, first name and last name.

    1 Enter name and email

  2. The Customer receives a voucher containing the payment details. In order to complete the payment, he needs to print the voucher and pay it at any PagoFácil / Rapipago / Provincia Pagos / CobroExpress branch in his area.

    1 Payment instructions

Globe GCash Test Data

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

Globe GCash Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters his Globe phone number.

    1 Enter phone number

  3. The customer receives an SMS from GCash and confirms the payment by responding with his received MPIN.

    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

Danske Test Data

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

Danske Payment Flow

  1. The customer fills the required details and confirms the payment.

    1 Enter payment details

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

    1 Return page when the redirection status is a success

Get information on a specific direct payment

You can get information about a one-off direct card payment by using GET HTTP request.

Definition: GET /v1/payments/{id}

Where:
  • {id} – GlobalPay Payment ID

Request:

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

Response:

HTTP/1.1 200 OK
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": null,
    "CreditCardToken": null,
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "Retry": false,
    "RedirectURL": null,
    "3DSecure": null
  }
}

Get the Status of a Direct Card Payment

You can get the status of a direct card payment by using the following GET HTTP request.

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

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

Where:
  • {id} – GlobalPay Payment ID

Request:

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

Response:

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

{
  "Payment": {
    "ID": 202230,
    "MerchantTransactionID": "s2ptest_h2",
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    }
  }
}

Cards Russia Test Data

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

Cards Russia Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer enters the card details: card number, expiration date and CVC.

    1 Card details

  3. The customer verifies the payment details, enters the same CVC and confirms the payment.

    1 Payment confirmation

  4. The customer receives the payment confirmation.

    1 Payment confirmation received

  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

Create a Complex Direct Card Payment

Definition: POST /v1/payments

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

A token is created and associated with the credit card and the payment.

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

Request:

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



{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h12",
    "OriginatorTransactionID": "100_a",
    "Amount": 2000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "BillingAddress": {
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Customer": {
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "Card": {
      "HolderName": "John Doe",
      "Number": "4111111111111111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018",
      "SecurityCode": "312"
    },
    "Capture": true,
    "Retry": true,
    "ReuseCreditCardToken": true
  }
}

Response:

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

{
  "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
  }
}

The token element received in the response can be used to initiate future payments, without having to enter all the necesary card details again. Also , the ID’s for the BillingAddress, ShippingAddress, and the Customer received in the initial response can be used to initiate future payments, without having to enter all the details again.

Request:

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


{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h13",
    "OriginatorTransactionID": "101_a",
    "Amount": 2000,
    "Currency": "EUR",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "BillingAddress": {
      "ID": 253
    },
    "ShippingAddress": {
      "ID": 87
    },
    "Customer": {
            "ID": 115
    },
    "CreditCardToken": {
      "Value": "6BEBF42B0E43D3BFD360DFB5EFF9D96D",
      "SecurityCode": "312"
    },
    "Capture": true,
    "Retry": true,
    "ReuseCreditCardToken": true
  }
}

Response:

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

{
  "Payment": {
    "ID": 202243,
    "ClientIP": null,
    "SkinID": null,
    "Created": "20161205093245",
    "MerchantTransactionID": "s2ptest_h13",
    "OriginatorTransactionID": "101_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": "Ends with 1111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018"
    },
    "CreditCardToken": {
      "Value": ""
    },
    "Status": {
      "ID": 11,
      "Info": "Captured",
      "Reasons": []
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": true,
    "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
Authorization: Basic MTAxMDpnYWJp

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_h14",
    "OriginatorTransactionID": "100_a",
    "Amount": 2000,
    "Currency": "EURO",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": "payment product",
    "StatementDescriptor": "bank statement message",
    "BillingAddress": {
      "City": "Iasi",
      "ZipCode": "7000-49",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "5A",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "ShippingAddress": {
      "City": "Iasi",
      "ZipCode": "700049",
      "State": "Iasi",
      "Street": "Sf Lazar",
      "StreetNumber": "37",
      "HouseNumber": "-",
      "HouseExtension": "-",
      "Country": "RO"
    },
    "Customer": {
      "MerchantCustomerID": "null",
      "Email": "customer@test.com",
      "FirstName": "John",
      "LastName": "Doe",
      "Gender": "1",
      "SocialSecurityNumber": "45908-28324",
      "Phone": "0744-783322",
      "Company": "S2P"
    },
    "Card": {
      "HolderName": "John Doe",
      "Number": "4111111111111111",
      "ExpirationMonth": "02",
      "ExpirationYear": "2018",
      "SecurityCode": "312"
    },
    "Capture": true,
    "Retry": true,
    "ReuseCreditCardToken": true
  }
}

Response:

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

{
  "Payment": {
    "InvalidRequestID": "i3067",
    "ID": null,
    "ClientIP": null,
    "SkinID": null,
    "Created": null,
    "MerchantTransactionID": "s2ptest_h14",
    "OriginatorTransactionID": "100_a",
    "Amount": 2000,
    "Currency": null,
    "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": null,
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Card": null,
    "CreditCardToken": null,
    "Status": {
      "ID": null,
      "Info": null,
      "Reasons": [
        {
          "Code": "1002",
          "Info": "Payment.Currency is invalid"
        }
      ]
    },
    "MethodTransactionID": null,
    "PaymentTokenLifetime": null,
    "Capture": null,
    "Retry": true,
    "RedirectURL": null,
    "3DSecure": null
  }
}

MTS Test Data

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

MTS Payment Flow

  1. The Customer enters his mobile phone number.

    1 Enter phone number

  2. A text message is sent to the customer in order to confirm the payment.

    1 Payment confirmation

  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

Beeline Test Data

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

Beeline Payment Flow

  1. The Customer enters his mobile phone number.

    1 Enter phone number

  2. A text message is sent to the customer in order to confirm the payment.

    1 Payment confirmation

  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

Klarna Checkout Test Data

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

Austria
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
Email address checkout-at@testdrive.klarna.com
Postal code 8071
First name Testperson-at
Last name Approved
Street Klarna-straße 1/2/3
House number 1
City Hausmannstätten
Phone number 0676 2600000
The information above is exemplary, any credentials will work
Denmark
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
The information above is exemplary, any credentials will work
Finland
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
Email address checkout-fi@testdrive.klarna.com
Postal code 28100
Personal identity number 190122-829F
Address Kiväärikatu 10
City Pori
Phone number 0401234567
Germany
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
Email address checkout-de@testdrive.klarna.com
Postal code 41460
First name Testperson-de
Last name Approved
Street Hellersbergstraße
House number 14
City Neuss
Phone number 01522113356
The information above is exemplary, any credentials will work
Norway
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
Email address checkout-no@testdrive.klarna.com
Postal code 0563
Personal identity number 01087000571
First name Testperson-no
Last name Approved
Address Sæffleberggate 56
City Oslo
Phone number 40 123 456
Sweden
Testing environment https://checkout.testdrive.klarna.com
Merchant ID (eid) and shared secret Please use the Merchant ID (eid) and shared secret provided to you by Klarna.
Email address checkout-se@testdrive.klarna.com
Postal code 12345
Personal identity number 410321-9202

Klarna Checkout Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer enters the postal code.

    1 Enter postal code

  3. The Customer fills in the form the required details for the billing address.

    1 Billing address

  4. The customer reviews the transaction details and confirms the payment.

    1 Payment confirmation

  5. The customer receives the payment confirmation.

    1 Payment confirmation received

  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

UnionPay Test Data

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

UnionPay Test Data
Credit Card Number: 6226388000000095
Mobile Phone: 18100000000
CVN2: 248
Expiration Date: Month/Year: 12/19
SMS Code on PC: 111111
SMS Code on Mobile: 123456

UnionPay Payment Flow

  1. The Customer chooses his preferred currency and enters his email address.

    1 Enter email

  2. The customer chooses the option to pay as a guest and enters his card number to proceed with the payment.

    1 Enter card number

  3. The customer enters the necessary card information. He also has to check and agree to The User Agreement of UnionPay and choose whether the card number to be remembered or not. After the customer verifies the information he clicks on the Confirm and Pay button.

    1 Enter card details

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

    1 Return page when the redirection status is Processing

Skrill Test Data

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

Skrill Test Data
Data Value
Email address skrill_user_test@smart2pay.com
Password Qazxsw21.
Skrill Test Credit Cards
Data Value
Mastercard 5438311234567890
Visa 4000001234567890
Amex 371234500012340

Please use only very small amounts, in order to keep the test account balance in check! After a test transaction, we recommend you to make a refund, so that your Skrill test account balance to be kept in check!

Skrill Payment Flow

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

    1 Customer details

  2. The customer logs in to his Skrill account by entering his email address and password.

    1 Account Login

  3. The customer sees his account balance and the amount to pay. He continues the transaction by clicking on the Pay Now button.

    1 Account Balance

  4. The customer receives the payment confirmation.

    1 Payment confirmation received

  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

Skrill 1_TAP Payment Flow

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

    1 Customer details

  2. The customer logs in to his Skrill account by entering his email address and password.

    1 Account Login

  3. The customer enters the required card details to make the payment, such as name, card number, expiration date and card CVV/CVC.

    1 Card details required

  4. The customer receives the payment confirmation.

    1 Payment confirmation received

  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

Bitcoin Test Data

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

Bitcoin Payment Flow

  1. The Customer enters his email address and name.

    1 Enter email

  2. The customer clicks Pay with Bitcoin to continue the payment.

    1 Pay with Bitcoin

  3. The customer’s preferred Bitcoin application opens automatically with the payment parameters prefilled.

    1 Bitcoin application login

  4. The customer has the possibility to monitor the status of the payment.

    1 Monitor status

  5. The customer can return to the merchant website by clicking “Return to Merchant” button.

    1 Return to merchant

  6. Upon completion of the payment flow, the customer is redirected to your ReturnUrl.

    1 Return page when the redirection status is Processing

Klarna Invoice Test Data

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

Austria
Private person Approved Denied
Gender male female
Date of Birth 14041960 14041980
First Name Testperson-at Testperson-at
Last Name Approved Denied
Street Klarna-Straße 1/2/3 Klarna-Straße 1/2/3
House Number
Zip Code 8071 8070
City Hausmannstätten Hausmannstätten
Phone Number 0676 2600000 0676 2800000
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Denmark
Private person Approved Denied
Personal Number 0801363945 0801373501
First Name Testperson-dk Testperson-dk
Last Name Approved Denied
Street Sæffleberggate 56,1 mf Sæffleberggate 56,1 mf
Zip Code 6800 6800
City Varde Varde
Phone Number 20 123 456 20 123 456
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Denmark
Company Approved Denied
Company Registration Number 27968880 99999993
Company Name Testcompany-dk Testcompany-dk
Street Sæffleberggate 56,1 mf Sæffleberggate 56,1 mf
Zip Code 6800 6800
City Varde Varde
Phone Number 20 123 456 20 123 456
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Finland
Private person Approved Denied
Personal Number 190122-829F 190122-333F
First Name Testperson-fi Testperson-fi
Last Name Approved Denied
Street Kiväärikatu 10 Kiväärikatu 10
Zip Code 28100 28100
City Pori Pori
Phone Number 0401234567 0401234567
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Finland
Company Approved Denied
Company Registration Number 10891871 07527622
Company Name Testcompany-fi Testcompany-fi
Street Kiväärikatu 10 Kiväärikatu 10
Zip Code 28100 28100
City Pori Pori
Phone Number 0401234567 0401234567
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Germany
Private person Approved Denied
Gender male female
Date of Birth 07071960 07071960
First Name Testperson-de Testperson-de
Last Name Approved Denied
Street Hellersbergstraße Hellersbergstraße
House Number 14 14
Zip Code 41460 41460
City Neuss Neuss
Phone Number 01522113356 01522113356
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Netherlands
Private person Approved Denied
Gender male female
Date of Birth 10071970 10071970
First Name Testperson-nl Testperson-nl
Last Name Approved Denied
Street Neherkade Neherkade
House Number 1 1
House Extension XI XI
Zip Code 2521VA 2521VA
City Gravenhage Gravenhage
Phone Number 0612345678 0612345678
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Norway
Private person Approved Denied
Personal Number 01087000571 01087000148
First Name Testperson-no Testperson-no
Last Name Approved Denied
Street Sæffleberggate 56 Sæffleberggate 56
Zip Code 0563 0563
City Oslo Oslo
Phone Number 40 123 456 40 123 456
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Norway
Company Approved Denied
Company Registration Number 999999999 811111112
Company Name Testcompany-no Testcompany-no
Street Sæffleberggate 56 Sæffleberggate 56
Zip Code 0563 0563
City Oslo Oslo
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Sweden
Private person Approved Denied
Personal Number 410321-9202 411028-8083
First Name Testperson-se Testperson-se
Last Name Approved Denied
Street Stårgatan 1 Stårgatan 1
Zip Code 12345 12345
City Ankeborg Ankeborg
Phone Number 0765260000 0765260000
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow
Sweden
Company Approved Denied
Company Registration Number 002031-0132 002032-0131
Company Name Testcompany-se Testcompany-se
Street #1 Stårgatan 1 Stårgatan 1
Zip Code #1 12345 12345
City #1 Ankeborg Ankeborg
Street #2 Lillegatan 1 Lillegatan 1
Zip Code #2 12334 12334
City #2 Ankeborg Ankeborg
Phone Number 0765260000 0765260000
Email youremail@email.com youremail@email.com
For a pending flow, please use the approved test person with one of these emails:
Pending → Approved pending_accepted@klarna.com Not available for the pending flow
Pending → Denied pending_denied@klarna.com Not available for the pending flow

Klarna Invoice 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.

    1 Enter payment details

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

    1 Return page when the redirection status is a success

MyBank Test Data

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

MyBank Payment Flow

  1. The Customer enters his email address, name and country, and chooses his preferred bank from the list.

    1 Select bank

  2. The customer enters the details required: login ID and password.

    1 Login details

  3. The Customer chooses the authentication mode.

    1 Authentication mode

  4. The customer views the transaction details and chooses an account.

    1 Select account

  5. The customer confirms the payment.

    1 Payment confirmation

  6. The customer receives the payment confirmation.

    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

eNETS Debit Test Data

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

eNETS Debit Payment Flow

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

    1 Enter email

  2. The customer needs to enter the correct payment details and he continues the payment by using the Submit button.

    1 Change details

  3. The customer chooses his preferred bank from the list.

    1 Select bank

  4. The customer logs in to his bank account by entering his User ID and PIN.

    1 Login details

  5. The customer receives a notification with the final status of the payment.

    1 Payment confirmation

  6. A printable receipt will appear in a separate browser window.

    1 Transaction receipt

  7. All the payment details will also appear in a new window of the browser.

    1 Payment details

Mazooma Test Data

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

Mazooma Payment Flow

  1. The Customer enters his email address, first name and last name.

    1 Enter email and name

  2. Once the customer arrives at provider’s page he chooses to Sign In. If he arrives at Sign Up area he must go to Sign In area.

    1 Sign In area

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

    1 Login details

  4. The customer logs in to his Test Bank online banking account by entering his User ID and password.

    1 Enter User Id

  5. The customer confirms the payment by using the Approve button.

    1 Payment confirmation

  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

MercadoPago Test Data

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

Test Users Brazil
Test User 1 Test User 2
ID 202010857 ID 202014799
Nickname TETE4663724 Nickname TETE5993983
Password qatest9001 Password qatest9857
Site_status Active Site_status Active
Email test_user_83022133@testuser.com Email test_user_4432956@testuser.com
Credit Cards Brazil
Card Type Card number
Visa 4235 6477 2802 5682
Mastercard 5031 4332 1540 6351
American Express 3753 651535 56885

MercadoPago Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer logs in to his MercadoPago account by entering his email address and password. If the customer doesn’t have a MercadoPago account yet, he will continue the payment as a guest.

    1 Login details

  3. The customer selects and verifies the payment option from the list, enters the card’s security code and confirms the payment.

    1 Payment details

  4. The customer receives a message that the payment was successfully approved and all the payment data will be send to the customer via his registered email address.

    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

Tenpay Test Data

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

Tenpay Payment Flow

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

    1 Select currency

  2. The customer needs to login to his Tenpay account with his account number and password.

    1 Login details

  3. The customer needs to confirm the payment by introducing the payment password.

    1 Payment password

  4. The customer receives a message that the payment was successfully processed.

    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

PayU Test Data

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

PayU (former DineroMail) Payment Flow

  1. The Customer selects the preferred currency from the list.

    1 Select currency

  2. The customer needs to enter his login details: full name and email address.

    1 Login details

  3. The customer chooses his preferred payment method from the list.

    1 Choose payment method

  4. After selecting his preferred method of payment, the customer needs to enter the necessary payment details. He then continues the payment by using the Pay button.

    1 Payment details

  5. The customer receives a message that the payment was successfully processed. The customer sees the payment summary and has the possibility to print or download the transaction details.

    1 Payment confirmation

  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

Credit Cards Colombia Test Data

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

Credit Cards Colombia 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 has to enter the required information. He has to fill out a form with the required card and customer details.

    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

OneCard Test Data

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

OneCard Payment Flow

  1. The Customer selects the preferred currency from the list.

    1 Select currency

  2. The customer logs in to his OneCard account with his email address and password.

    1 Login details

  3. The customer confirms the payment by clicking on the Yes button.

    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

TELE2 Test Data

In order for you to test the TELE2 payment method successfully, you don’t need any given test data.

TELE2 Payment Flow

  1. The Customer enters his phone number belonging to TELE2 mobile operator. Depending on the customer’s amount of his phone balance, his payment request will be approved or declined.

    1 Enter phone number

  2. 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-in Test Data

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

Cash-in Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer enters his phone number and email address.

    1 Login details

  3. The Customer receives the payment code with which he can complete the payment at any ATM or office. He also has the possibility to print the payment instructions.

    1 Payment instructions

Cash Option Thailand Test Data

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

Cash Option Thailand Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer enters his name and surname and he can choose to receive the paycode via sms.

    1 Login details

  3. The customer receives the printable payment details and the instructions that he has to follow in order to make the payment. He can finish the transaction by clicking on Done button.

    1 Payment instructions

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

    1 Return page when the redirection status is Processing

PaysBuy Wallet Test Data

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

PaysBuy Wallet Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer logs in to his PaysBuy account with his email and password.

    1 Login details

  3. The customer sees the payment details and confirms 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

Online Banking Thailand Test Data

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

Online Banking Thailand Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer chooses the payment method and enters the details required in order to login to his bank.

    1 Login details

  3. The customer sees the payment details and confirms the payment by clicking on the Continue button.

    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

Boleto Bancário Test Data

In order for you to test Boleto Bancário payment method successfully, you don’t need any given test data.

Boleto Bancário Payment Flow

  1. The customer enters his name and email address.

    1 Enter name and email

  2. The customer receives the Boleto with all the necessary payment details. In order to complete the payment, he needs to print the Boleto and go to a physical bank branch in his area and pay with cash, use online banking, or simply go to an ATM machine.

    1 Print Boleto

QIWI Wallet Test Data

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

QIWI Wallet Payment Flow

  1. The Customer chooses his preferred currency from the list and enters his phone number.

    1 Enter phone number

  2. The Customer enters his QIWI Wallet password before proceeding with the payment.

    1 Login details

  3. The customer sees his account balance and the amount to pay. He continues the transaction by clicking on the Pay button.

    1 Account details

  4. The customer confirms the transaction by entering the one time pass code received via SMS.

    1 Payment confirmation

  5. The customer receives the payment confirmation.

    1 Payment confirmation received

  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

Pay by Mobile Test Data

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

Pay by Mobile Test Data
Data Value
Network operator Enter any network operator from the list: Vodafone, Orange, T-mobile.
Phone number: Enter any 9 digit number. Example: (+40) 745123456

Pay by mobile Payment Flow

  1. The Customer selects his network operator and enters his phone number.

    1 Enter phone number

  2. The customer receives the payment confirmation.

    1 Payment confirmation

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

    1 Return page when the redirection status is Processing

VoguePay Test Data

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

VoguePay Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer logs in to his VoguePay account with his username or email and password.

    1 Login details

  3. The customer receives the payment confirmation.

    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

Yandex.Money Test Data

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

Yandex.Money Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  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

PagoEfectivo Test Data

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

PagoEfectivo Payment Flow

  1. The customer chooses the transaction currency and enters the required details. He completes the transaction by clicking on the Continue button.

    1 Payment details

  2. The customer receives the printable instructions that he has to follow in order to make the payment.

    1 Payment instructions

INTERAC@Online Test Data

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

INTERAC@Online Payment Flow

  1. The Customer enters the required details to make the payment, such as name, email, phone number and billing address.

    1 Payment details

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

    1 Return page when the redirection status is Processing

Cards Test Data

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

Cards Test Data
Data Value
Card Number (VISA): 4111111111111111
Expiration Date: Choose a month and a year at least equal than the current month and year
Card CVV/CVC: Any 3 digit number. Example: 123

Cards Payment Flow

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

    1 Enter email and name

  2. The customer enters the required card details to make the payment, such as name, card number, expiration date and card CVV/CVC.

    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

MTCPay Test Data

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

MTCPay Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer logs in his MTCPay account with his username and password. He also has to enter the code given in the security box before proceeding with the payment.

    1 Login details

  3. The customer sees the payment summary and he completes the transaction by clicking on the Pay button.

    1 Confirm transaction

  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

MangirKart Test Data

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

MangirKart Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the 16 digit PIN. He also has to check and agree to the Terms of MangirKart before proceeding with the payment.

    1 Login details

  3. The customer sees the payment summary and details. He completes the transaction by clicking on the Pay button.

    1 Confirm transaction

  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

ToditoCash Test Data

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

ToditoCash Payment Flow

  1. The customer enters his email address, his name and the necessary card details, such as Card number and PIN. He completes the transaction by clicking on the Continue button.

    1 Payment details

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

    1 Return page when the redirection status is a success

PaySafeCard Test Data

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

PaySafeCard Payment Flow

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

    1 Enter email

  2. The Customer enters the 16 digit PIN. He also has to check and agree to the Terms of Paysafecard before completing the payment.

    1 Payment confirmation

  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

Cards Brazil Test Data

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

Cards Brazil Payment Flow

  1. The customer chooses his card brand and enters the necessary card details. He completes the transaction by clicking on the Continue button.

    1 Payment details

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

    1 Return page when the redirection status is a success

PaysBuy Test Data

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

PaysBuy Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the login details. He must fill the form with his email and password and click the Login button.

    1 Login details

  3. The Customer confirms the payment by introducing the One-time password (OTP).

    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

Transactions

With your GlobalPay Dashboard Account you can see reports about your transactions and also manage your sites.

Access Dashboard Account to view the reports of the transactions you completed.

GlobalPay Dashboard Account is your tool not only to see reports about your transactions, but also to create or configure your websites, initiate refunds and operate the transactions (possible actions: view, filter, search, export in Excel format).

For more information on how you can operate with GlobalPay Dashboard please go to our GlobalPay Merchant Dashboard Guide.

POLi Test Data

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

POLi Test Data
Data Value
User DemoShopper
Password DemoShopper

POLi Payment Flow

  1. The Customer selects his Bank from the list and proceeds with the payment.

    1 Select bank

  2. The Customer enters the login details. He must fill the form with his Username and password and click the Login button.

    1 Login details

  3. The Customer needs to select the bank account he wants to transfer money from and click the Continue button.

    1 Select bank account

  4. The customer is redirected to the provider’s confirmation page where he sees the payment summary and details. He completes the transaction by clicking on the Confirm button.

    1 Transaction 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

Abaqoos Test Data

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

Abaqoos Payment Flow

  1. The Customer sees the calculated amount and he needs to confirm the payment by using the Continue button.

    1

  2. The Customer logs in to his Abaqoos account with his username and password and clicks the Enter button.

    1 Login details

  3. The customer sees the payment summary and details. He completes the transaction by clicking on the Start Transaction button.

    1 Start transaction

  4. The customer is redirected to the provider’s confirmation page where a text message will appear in a window. He confirms the transaction by clicking on the OK button.

    1 Transaction 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

Paysera Test Data

In order for you to test the Paysera payment method successfully, you don’t need any given test data.

Paysera Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer needs to check the country from the list and select a bank where he will pay.

    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

Moneta.ru Test Data

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

Moneta.ru Payment Flow

  1. The Customer selects the preferred currency from the list.

    1 Select currency

  2. The Customer enters the login details. He must fill the form with his email and password and continue the transaction using the Next button.

    1 Login details

  3. The Customer selects the bank account he wants to transfer money from and continue the transaction using the Next button.

    1 Select bank account

  4. The Customer enters the password of the payment and uses the Pay button to finish the payment.

    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

CashU Test Data

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

CashU Test Data
Data Value
Account ID: JwLqCa621762953@cashUcard.com
Password: 67l6Yoyied115

For test purposes, please initiate payments using only small amounts.

CashU Payment Flow

  1. The Customer selects the preferred currency from the list.

    1 Select currency

  2. The Customer enters the payment details. He must fill the form with his CashU Account ID and password and enter the code given in the security box.

    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

Multibanco SIBS Test Data

In order for you to test Multibanco SIBS payment method successfully, you don’t need any given test data.

Multibanco SIBS Payment Flow

  1. The Customer receives the printable payment details which he can use to make the payment at a Multibanco ATM, internet banking or mobile phone.

    1 Payment details

  2. 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 Transfer Test Data

In order for you to test Bank Transfer payment method successfully, you don’t need any given test data.

Bank Transfer Payment Flow

  1. The customer will be redirected to the payment page where he enters his name.

    1 Enter name

  2. The customer receives the details to make the payment of the transaction. He also has the possibility to print the payment details.

    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

  • There is another possibility to complete a Bank Transfer payment flow where you can send your own Reference Number in the request.
  1. The customer will be redirected to the payment page where he enters his name.

    1 Enter name

  2. The customer receives the payment details with your own Reference Number. He also has the possibility to print the payment details.

    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

  • There is even one more simple possibility to complete a Bank Transfer payment flow where you can display the payment instructions on your own page by sending the mandatory parameter Customer and use the information received in Response for ReferenceDetails.
  1. The customer will see and complete the payment instructions on your own page.

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

    1 Return page when the redirection status is a success

Nordea Test Data

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

Nordea Test Data
Data Value
User ID 123456
Password 1234
Confirmation code Any 3 digit number

Example: 123

Nordea Payment Flow

  1. The Customer enters the payment details. He must fill the form with his User ID and password. The test User ID is 123456 and the test password is 1234.

    1 Payment details

  2. The customer enters the confirmation code and confirms the payment. The test confirmation code is formed by any 3 digit number, example: 123.

    1 Payment confirmation

  3. The customer is redirected to the provider’s confirmation page where he sees the payment details.

    1 Payment confirmation

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

    1 Return page when the redirection status is Success

OP-Pohjola Test Data

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

OP-Pohjola Test Data
Data Value
User ID: 123456
Password: 7890
Key number: Enter any number.

Example: 123

OP-Pohjola Payment Flow

  1. The Customer enters his username and password for identification.

    1 Identification

  2. The Customer enters the key number. For test purposes, please enter the 4 digit number given in the form.

    1 Payment details

  3. The customer is redirected to the provider’s confirmation page where he sees the payment summary and details.

    1 Payment confirmation

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

    1 Return page when the redirection status is Success

Finnish Banks Test Data

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

Finnish Banks Test Data
Bank Name Data Value
Nordea User ID 123456
Password 1234
Confirmation code Any 3 digit number

Example: 123

OP-Pohjola (Osuuspankin) User ID 123456
Password 7890
Key number Any number

Example: 123

Ålandsbanken User ID 12345678
Password 1234
Key number Any 4 digit number

Example: 1234

Handelsbanken User ID 11111111
Password 123456
Security code 123456

POP Pankki User ID 11111111
Password 123456
Security code 123456

Säästöpankki User ID 11111111
Password 123456
Security code 123456

Oma Säästöpankki User ID 11111111
Password 123456
Security code 123456

The MethodOptionID parameter for Finnish Banks method can have the following values:

Finnish Banks Method Option IDs
Method Option ID Description
60 Nordea
61 OP-Pohjola (Osuuspankki)
62 Danske
64 Ålandsbanken
65 Handelsbanken
67 S-Pankki
298 Aktia
299 POP Pankki
300 Säästöpankki
322 Oma Säästöpankki

Finnish Banks Payment Flow

  1. The Customer chooses his Bank from the list.

    1 Bank selection

  2. The Customer enters the payment details. He must fill the form with his User ID and password. The test User ID is 123456 and the test password is 1234.

    1 Payment details

  3. The customer enters the confirmation code and confirms the payment. The test confirmation code is formed by any number; example: 123

    1 Payment confirmation

  4. The customer is redirected to the provider’s confirmation page where he sees the payment details.

    1 Payment confirmation

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

    1 Return page when the redirection status is Success

WebMoney Japan Test Data

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

WebMoney Japan Test Data
Prepaid Number Type
1111111111111111 Successful transaction
e111111111111112 Invalid card number
e111111111111113 Prepaid card has already been used
e111111111111114 Card has been declined due to an unknown error

WebMoney Japan Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the payment details. He must fill the form with a valid Prepaid Number. For test purposes, please type the 16 digit prepaid number: 1111-1111-1111-1111, for a successful transaction.

    1 Payment details

  3. The customer is redirected to the provider’s confirmation page where he also sees the payment summary.

    1 Payment confirmation

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

    1 Return page when the redirection status is Success

PayEasy Japan Test Data

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

PayEasy Japan Test Data
Data Value
Last Name: Enter any name
First Name: Enter any name
Phone Number: Enter any 10 digit number.

Example: 1234567812

PayEasy Japan Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the payment details. He must fill the form with his last name, first name and a valid phone. For test purposes, please provide any first and last name and also any 10 digit phone number.

    1 Payment details

  3. The customer is redirected to the provider’s confirmation page where he sees the payment summary and details. He will also receive an email containg further instructions for completing the purchase.

    1 Payment instructions

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

    1 Return page when the redirection status is Processing

Konbini Test Data

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

Konbini Test Data
Data Value
Phone Number: Enter any 10 digit number starting with: 05, 06, 07, 08 or 09.

Example: 0912121212

Konbini Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer must provide a phone number and choose a Konbini store where he wants to pay. For test purposes, please provide any 10 digit phone number starting with: 05, 06, 07, 08 or 09 and choose any Konbini store from the list.

    1 Payment details

  3. The customer is redirected to the provider’s confirmation page where he sees the payment summary and details. He will also receive an email containg further instructions for completing the purchase.

    1 Payment instructions

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

    1 Return page when the redirection status is Processing

Cards Japan Test Data

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

Cards Japan Test Data
Data Value
Last Name: Enter any name
First Name: Enter any name
Credit Card Number: JCB: 3530111333300000
American Express: 378282246310005
VISA: 4111111111111111
Master Card: 5555555555554444
Diners Club: 30569309025904
Insufficient funds: 4123111111111000
Exceeds card limit: 4123111111111018
Bad verification value: 4123111111111034
Card expired: 4123111111111042
Cannot use card: 4123111111111059
Invalid card: 4123111111111067
Card Security Code: Any 3 digit number. Example: 123
Expiration date: Choose a month and a year at least equal than the current month and year

Cards Japan Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the payment details. He must fill the form with his last name, first name and a valid credit card number. For test purposes, please provide any first and last name and one of the test credit card numbers given above.

    1 Payment details

  3. The customer is redirected to the provider’s confirmation page.

    1 Payment instructions

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

    1 Return page when the redirection status is Success

Bank Transfer Japan Test Data

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

Bank Transfer Japan Test Data
Data Value
Last Name: Enter any name.
First Name: Enter any name.
Phone Number: Enter any 10 digit number. Example: 1234567812

Bank Transfer Japan Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The Customer enters the payment details. He must fill the form with his last name, first name and a valid phone. For test purposes, please provide any first and last name and also any 10 digit phone number.

    1 Payment details

  3. The Customer sees the payment summary and details. He will receive an email containing further instructions for completing the purchase.

    1 Payment instructions

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

    1 Return page when the redirection status is Processing

PayWithMyBank Test Data

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

PayWithMyBank Test Data
Bank Name: Demo Bank
User: Enter any user. Example: 12345678
Password: Enter any number. Example: 12345
Account: Demo Checking Account

PayWithMyBank Payment Flow

  1. The Customer enters his email address and name.

    1 Enter email and name

  2. The Customer selects his Bank and enters his login details: username and password.

    1 Login details

  3. The Customer chooses an account and confirms the payment. For test purposes, please choose Demo Checking account.

    1 Payment confirmation

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

    1 Return page when the redirection status is Processing

DragonPay Test Data

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

DragonPay Test Data
Online Banking Bank Name: Bogus Bank
Login ID: pwd
Password: pwd
Over-the-Counter / ATM banking Bank Name: Bogus Bank Over-the-Counter
You will get an email and you will follow the link and confirm the payment

DragonPay Payment Flow

  1. The Customer enters his email address.

    1 Enter email

  2. The customer selects his bank. For test purposes, please select for Online Banking: Bogus Bank, and for Over-the-Counter/ATM Banking: Bogus Bank Over-the-Counter.

    1 Bank selection

  3. The customer enters his login details. The test Login ID is pwd and the test password is pwd.

    1 Login details

  4. The customer selects his available bank account. For test purposes, please select one of the bank accounts given in the form.

    1 Bank account selection

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

    1 Return page when the redirection status is a success

P24 Test Data

In order for you to test P24 (Przelewy24) payment method successfully, please use the below test data.

P24 Test Data
To send in description Value
For Success TEST_OK
For Failed TEST_ERR04, TEST_ERR102, TEST_ERR106

P24 Payment Flow

  1. The customer enters his email address.

    1 Enter email

  2. The customer selects his Bank from the list.

    1 Bank selection

  3. The customer can see all the details of the payment provided in the form and he can further confirm the payment by clicking on the pay button.

    1 Payment confirmation

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

    1 Return page when the redirection status is a success

MrCash Test Data

MrCash payment method doesn’t have yet any available test data for use. But you can see how it works with the below standard payment flow.

MrCash Payment Flow

  1. The Customer introduces the details required.

    1 Login details

  2. The customer needs to confirm the payment by entering his identification password.

    1 Enter identification password

  3. The customer is redirected to the provider’s confirmation page where the identification process is confirmed.

    1 Identification ok

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

    1 Return page when the redirection status is a success

Delete a Website

Definition: DELETE /v1/merchantsites/{id}

Where:
  • {id} – GlobalPay Website ID

You can delete a website by sending a DELETE action for an existing website for which there are not registered yet any payments.

Request:

DELETE https://paytest.smart2pay.com/v1/merchantsites/1000022
Authorization: Basic MTAwMDAyMjo0aGNjU2lMVjU2QlYwSWR1YUZ2Ynp2YUdFQWRHOEJodjIwaEFndjdrVE9aTmU0S0loQg==

Response:

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

{
  "MerchantSite": {
    "MerchantID": 1045,
    "ID": 1000022,
    "Created": "20160317115423",
    "URL": "http://www.testupdate.com",
    "Active": true,
    "NotificationURL": "http://www.test.com/notifications_update.node",
    "ApiKey": "4hccSiLV56BV0IduaFvbzvaGEAdG8Bhv20hAgv7kTOZNe4KIhB",
    "Alias": "Test website update_1000022",
    "IPList": "82.208.151.136",
    "Details": {
      "Reasons": null,
      "Name": "Stichting Smart2Pay update",
      "Country": "PL",
      "City": "Warsaw update",
      "Email": "test@test.com",
      "Address": "BRINK 27C update",
      "BankName": "ING",
      "AccountIBAN": "PL641050008610000023537933350",
      "AccountSWIFT": "1000002353794650",
      "BankSWIFTID": "ABNDDEFFXXX",
      "BankCode": "BTRLRO22",
      "VATNumber": "34206701",
      "RegistrationNumber": "NL 813236460B01"
    }
  }
}

TrustPay Test Data

In order for you to test TrustPay payment method successfully, you don’t need any given test data. You only need to provide a valid email address.

TrustPay Payment Flow

  1. The Customer fills the form with his email and selects his preferred currency.

    1 Enter email

  2. The Customer selects his Bank from the list.

    1 Select bank

  3. The Customer pays the transaction having the option to pay now or later.

    1 Pay transaction

  4. The customer confirms the transaction by clicking on the Ok button.

    1 Transaction confirmation

  5. The customer is redirected to the provider’s confirmation page.

    1 Confirmation page

  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

Create a Payment

Definition: POST /v1/payments

To initiate a payment, you must create a payment object. The parameters of the payment are sent in the message body as a JSON object.

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

Request: 

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

{
  "Payment": {
    "MerchantTransactionID": "s2ptest_g2",
    "Amount": 11,
    "Currency": "CNY",      
    "MethodID": 1066,
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",      
    "TokenLifetime": 10,
    "Customer": {    
      "Email": "youremail@email.com"   
    } 
  }
}

Response:

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

{
  "Payment": {
    "ID": 2677982,
    "SkinID": null,
    "ClientIP": null,
    "Created": "20161107092103",
    "MerchantTransactionID": "s2ptest_g2",
    "OriginatorTransactionID": null,
    "Amount": 11,
    "Currency": "CNY",
    "ReturnURL": "http://demo.smart2pay.com/redirect.php",
    "Description": null,
    "MethodID": 1066,
    "MethodOptionID": null,
    "IncludeMethodIDs": null,
    "ExcludeMethodIDs": null,
    "PrioritizeMethodIDs": null,
    "SiteID": 30201,
    "NotificationDateTime": null,
    "Customer": {
      "ID": 473,
      "MerchantCustomerID": null,
      "Email": "youremail@email.com",
      "FirstName": null,
      "LastName": null,
      "Gender": null,
      "SocialSecurityNumber": null,
      "Phone": null,
      "Company": null,
      "DateOfBirth": null
    },
    "BillingAddress": null,
    "ShippingAddress": null,
    "Articles": null,
    "Details": null,
    "ReferenceDetails": {
      "BankCode": null,
      "BankName": null,
      "EntityID": null,
      "EntityNumber": null,
      "ReferenceID": null,
      "ReferenceNumber": null,
      "SwiftBIC": null,
      "AccountCurrency": null,
      "AccountNumber": null,
      "AccountHolder": null,
      "IBAN": null,
      "QRCodeURL": "weixin://wxpay/bizpayurl?pr=ad7EqGN"
    },
    "CustomParameters": null,
    "PreapprovalID": null,
    "Status": {
      "ID": 1,
      "Info": "Open",
      "Reasons": null
    },
    "MethodTransactionID": null,
    "TokenLifetime": 10,
    "Capture": null,
    "RedirectURL": "https://apitest.smart2pay.com/Home?PaymentToken=8455FA9767A0795E6DDAD87775B8B10E.2677982"
  }
}

In order to initiate a Direct Card payment, the payment object must contain 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
  }
}