# JPMC-PDP Documentation from https://developer.payments.jpmorgan.com

# Trustly

Trustly is a real-time bank transfer payment service that allows consumers to quickly and easily complete a transaction without ever leaving your website or app. These bank-to-bank transactions don’t carry the same processing and interchange fees that credit cards do, which means your company can retain more revenue. 

## Availability

 
**Trustly availability**

| Payment method | Payment type | Consumer (country) | Merchant (country) | Presentment currency | 
| --- | --- | --- | --- | --- | 
| Trustly | Bank transfer | AT, DE, DK, EE, ES, FI, GB, LT, LV, NL, NO, SE | AT, BE, CH, CY, CZ, DE, DK, ES, FI, FR, GB, GG, GI, IE, IM, IT, JE, LU, MT, NL, NO, PT, SE | EUR, GBP, SEK | 

## Branding guidelines

For branding guidelines from Trustly, go [here](https://brandguidelines.trustly.net/).

## How Trustly works

Trustly streamlines the payment experience and minimizes processing costs. In general, the payment process follows these steps:

1. Your consumer selects Trustly as their preferred payment method from your payment page.

2. You initiate a POST request to the /payments endpoint to submit the payment to Trustly. Ensure the paymentMethodType attribute is set to trustly.

3. J.P. Morgan returns the Trustly redirect URL to you.

4. You return the Trustly redirect URL to your consumer's browser.

5. Your consumer authenticates their payment using their bank account login credentials.

6. After the consumer has approved the payment, J.P. Morgan returns confirmation of the payment result to you.

> You are notified of the payment result through webhook notifications. To learn more, check out the [Notifications API](/docs/commerce/optimization-protection/capabilities/notifications/index).
> 

## Required fields

The following fields are required for Trustly:

 
**Required fields for Trustly**

| Field name | Description | 
| --- | --- | 
| amount | Total monetary value of the payment including all taxes and fees. | 
| currency | Identifier of the currency for the amount fields. This is the 3 character ISO 4217 currency code. | 
| merchant.merchantSoftware.companyName | The company name of the software integrated to this API. If merchant is directly integrated, send JPMC. | 
| merchant.merchantSoftware.productName | The name of the product used for marketing purposes from the consumer's perspective. | 
| merchant.merchantSoftware.version | Designates the unique state of computer software as it is developed and released. The version identifier can be a word, a number, or both. | 
| softMerchant.name | The name of the merchant recognizable to an account holder. This is used when the merchant of record is a payment facilitator. | 
| softMerchant.address.line1 | First line of the street address. | 
| softMerchant.address.line2 | Second line of the street address. | 
| softMerchant.address.city | The name of the municipality. | 
| softMerchant.address.state | The name of the state or province. | 
| softMerchant.address.postalCode | The portion of a party’s address that is the encoded representation of a geographic area to facilitate mail delivery services. | 
| softMerchant.address.countryCode | The country code of the address based on Alpha 3 ISO standards. | 
| accountHolder.email | The email address of the account holder. | 
| accountHolder.billingAddress.line1 | First line of the street address. | 
| accountHolder.billingAddress.postalCode | The portion of a party’s address that is the encoded representation of a geographic area to facilitate mail delivery services. | 
| accountHolder.billingAddress.countryCode | The country code of the address based on Alpha 3 ISO standards. | 
| merchantOrderNumber | A unique merchant assigned identifier for the confirmation of goods and/or services purchased. | 
| statementDescriptor | The merchant name to appear on the account holder statement. | 
| paymentMethodType.trustly.preferredLanguage | Language preference of the consumer for the pages displayed using language tags indicated in RFC5646. | 
| paymentMethodType.redirectedPayment.merchantReturnUrl | Information on where the consumer needs to be redirected after payment process completion. Ensure that the URL begins with 'https'. | 

> A few things to keep in mind:
> 
> 
> - To support a guest shopping experience where you do not have access to the consumer's information, set the accountHolder.fullName to guest shopper and send your country code in accountHolder.billingAddress.countryCode.
> 
> - Provide accountHolder.email for enhanced return customer experience, reduced friction, and increased conversion. If a value is not available, the field can be left blank.
> 

## Related

[Payments methods](/docs/commerce/online-payments/capabilities/online-payments/payment-methods/index)
 [Authorize and capture a payment](/docs/commerce/online-payments/capabilities/online-payments/how-to/auth-and-capture-payment)
 [Notifications API](/docs/commerce/optimization-protection/capabilities/notifications/index)