WHY FOR THE PAYMENT SDK DEVELOPER DEVELOPER?

How 3D Secure works

Most often, the 3-D Secure protocol in work looks like this: you make a payment on the website or in the store, enter the card details, then go to the page of the issuing bank, where you enter the code received in SMS. After that, your payment is completed successfully.

The name 3-D comes from 3-Domain (three domains), since organizations on three domains participate in the payment verification under this protocol: the issuer’s domain (payer and issuing bank), the acquirer’s domain (payment processing bank, and online store) ) and the interaction domain (MPS). This is how a simplified payment verification scheme using the 3-D Secure protocol looks like:

The payer enters the card data in the online store, they reach the acquiring bank (1), are sent to the MPS (2), from where they are sent to the issuing bank (3). You can find out which bank issued the card by the first six digits of the card number. The issuing bank reports that the card is subscribed to 3-D Secure, generates a unique code, as well as a link to the code entry page (4). The link is returned to the TSP or IPSP (5), which redirect the card holder to this page in the browser (6,7). At this point, the issuer sends the cardholder via another channel (for example, via SMS) the code that he enters on the page. If the code is entered correctly, the issuing bank reports on the successful completion of the check (8), and the funds are debited from the payer's card (9, 10).

FIELD NOTES: USING THE PAYMENT SDK

Code example

private void Pay() 
{ 
var conf = new Configuration 
{ 
MerchantId = 1, 
Key = "PrivateKey", 
}; 
var request = new PayRequest 
{ 
Amount = 30m, 
Currency = Currency.Rub, 
OrderId = "335636462808", 
CardExpMonth = 1, 
CardExpYear = 2018, 
CardCvv = 100, 
CardHolderName = "CARD HOLDER", 
CardNumber = "4111111111111111", 
Email = "cardholder@example.com", 
}; 
var po = new Processing(conf); 
po.ThreeDs += po_ThreeDs; 
po.Success += po_Success; 
po.Decline += po_Decline; 
po.Error += po_Error; 
po.Pay(request); 
} 
void po_Error(object sender, Exceptions.PaymentSDKException e) 
{ 
} 
void po_Decline(object sender, PayResponse e) 
{ 
} 
void po_Success(object sender, PayResponse e) 
{ 
} 
void po_ThreeDs(object sender, PayResponse e) 
{ 
((Processing)sender).NavigateToAcsUrl(Browser, e); 
} 
class Configuration : IConfiguration 
{ 
public int MerchantId { get; set; } 
public string Key { get; set; } 
}

What's going on here

class Configuration : IConfiguration 
{ 
public int MerchantId { get; set; } 
public string Key { get; set; } 
}

• Success - arises in case of successful payment.
• Decline - arises in case of refusal to conduct.
• Error - if any errors occurred at the time of payment, for example, the network is unavailable.
• ThreeDs - An additional 3-D Secure check is required.

• Amount - payment amount.
• Currency - currency (rubles, US dollars and euros are supported).
• OrderId - ID of the order that you generate in your system.
• CardExpMonth - card expiration month.
• CardExpYear - card expiration year.
• CardCvv - CVC2 / CVV2.
• CardHolderName is the name of the card holder.
• CardNumber - card number.
• Email - payer's e-mail.

Regular payments and one-click payments

1. The user once agrees to the conditions of automatic charge-off (for example: 100 rubles every 3 months), enters the card data and makes the first payment. Further charges are made without the participation of the client.
2. The user enters the card data at the first payment in the application. Further payments are made without entering card data, but with the participation of the payer. 3D Secure verification may occur or CVV input will depend on the settings.

Interface

void Rebill(RebillRequest request);

Universal Apps Support

Switching to Universal Apps Technology

After downloading the project, the studio proposed adding support for Windows 8.1

Solution Explorer selects Retarget Windows Store projects to Windows 8.1

Then, in the project properties in the Targeting property, they selected support for Windows 8.1 and Windows Phone 8.1

About Payment SDK Development Plans