POST Create a Transaction
POST /transfer/v1/transactions
Development Guide
The 'Create a Transaction' endpoint determines what information to collect from the consumer, validates the data for compliance purposes and updates the transactionId resource with the data gathered.
1. Prepare headers & authentication:
The application must call the 'Update a transaction' endpoint with a POST HTTP method, providing the OAuth access_token in the header and all other required header values.
Note: MoneyGram uses the OAuth 2.0 framework. The application must use their OAuth client credentials to generate an
access_tokenby calling the Get access token endpoint. The token is valid for **1 hour ** and must be passed as a header value in all subsequent API HTTP calls. Learn More
Launch Code ExampleTransfer Create - HeadersOpen Recipe
2. Provide request body: "Transact by send amount" OR "Transact by receive amount":
The application must use the oneOf Keyword to update a transaction by send or receive amount.
- **Transact by send amount: **The application must provide the following required fields in the request body:
targetAudience,agentPartnerId,destinationCountryCode,serviceOptionCode,sendAmount.value,sendAmount.currencyCode, andreceiveCurrencyCode.
OR
- **Transact by receive amount: ** The application must provide the following required fields in the request body:
targetAudience,agentPartnerId,destinationCountryCode,serviceOptionCode,receiveAmount.value,receiveAmount.currencyCode, andsendCurrencyCode
Note:
- If the application leaves the
serviceOptionCodefield empty, all service options to thedestinationCountryCodewill be returned (i.e. cash pickup, bank, wallet & card deposit). Learn More- The Quote API uses ISO Standards for country and currency values. MoneyGram provide Reference Data APIs which can be queried to understand and list the supported values and associated metadata.
Launch Code ExampleTransfer Create - By Send AmountOpen Recipe.
Transfer Create - By Receve AmountOpen Recipe
3. Provide sendersender, receiver & transactionDetails to the request body:
sender, receiver & transactionDetails to the request body:The application must collect sender, receiver, and transactionDetails for MoneyGram to perform real-time validation and compliance screening. At a minimum the following required fields are needed:
sender.name.firstName,sender.name.lastName,sender.address.line1,sender.address.city,sender.address.countryCode,sender.mobilePhone.number,sender.mobilePhone.countryDialCode,personalDetails.dateOfBirth,primaryIdentification,receiver.name.firstName,receiver.name.lastName
Note: To understand a full list of REQUIRED and OPTIONAL fields, the application can call the Retrieve Fields for a Transfer API. Learn More
Launch Code ExampleTransfer Create - Personal & Transaction DetailsOpen Recipe
4. Provide targetAccount fields to the request body for bank, wallet or card deposit (optional):
targetAccount fields to the request body for bank, wallet or card deposit (optional):The account's information can be can be submitted through the targetAccount dynamic key/value pairs.
Note: To understand the which account deposit fields are required to collect from the consumer, see the Bank & Wallet Coverage guide, or the application can use the Retrieve Fields for a Transfer API to determine the list of account fields.
Launch Code ExampleTransfers Create - Account Details (OptionalOpen Recipe
5. Make a request and handle response:
The application must call the 'Create a Transaction' endpoint with a POST HTTP method. The application must build to handle the following response scenarios:
- Success | Parse the Response | 200 OK HTTP Status |
"readyToCommit": true
When the 'Update a transaction' endpoint responds with a 200 HTTP Status and the"readytoCommit": true,transactionId,serviceOption,sendAmount,sendCurrency,fees,fxRate,discountsAppliedand thereceiveAmount. In some cases, send or receive side taxes are applied. The application can proceed to "Commit a transaction" API and execute the transfer of funds.
- Failed | Handle the Error | 400 Bad Request HTTP Status
When the 'Update a transaction' endpoint responds with 400 Bad Request HTTP Status the application cannot proceed to the "Commit a Transaction" endpoint. Specific error code/s will be returned with an array of offending fields. The application will need to resolve these errors and resubmit the transaction for validation. The application can make repeated attempts on the 'Update a transaction' endpoint until validation is successful.
Note: In some scenarios, enhanced due diligence needs to be undertaken on the consumer. Specific error code/s will be returned and an array of offending fields. The fields/values must to be provided and resubmitted on the Update API for further checks.
Launch Code ExampleTransfer Create - SuccessOpen Recipe.
Transfer Create - FailureOpen Recipe
6. You're Done! Proceed to 'Commit a Transaction API':
The application can call the 'Commit a transaction' endpoint to execute the transfer when a 200 HTTP Success Status and the boolean "readyForCommit": true is returned on the Create response. The application must use the associated transactionId on the subsequent Commit API by providing it as a path parameter. The Commit endpoint is the final API call and will execute the transaction to MoneyGram.
Note: the application cannot proceed until the
"readyForCommit": true. The Application must correct and resubmit the data to until they get a"readyForCommit": true
Business Rules to Code
- Updating the
transactionId: If there are any changes needed for consumer data after the Create API, the application should call the Update a Transaction' endpoint using a PUT Http method, providing thetransactionIdas path parameter and provide new consumer/transactional data in the request body. Learn More
- **Enumerated fields: **For all Enumerated Fields (some examples below), agent application must use the valid enumerations returned from the enumerations API response and allow only valid values to be selected. Learn More
- Start online, fund in store: For digital application wanting to fund the transactions in store, set the
"fundInStore": true.
- Telemarketing (US ONLY): It is regulatory requirement in the USA (only) to display a telemarketer notice to the start of every transaction, on every transfer, in every country and for every service option. The Telemarketer Notice must be displayed to the consumer before quoting the transaction on the Quote API. Learn More
- Fraud Warnings: It is regulatory requirement to show Fraud Warnings on every transfer, in every country and for every service option. The Fraud Warnings must be displayed to the consumer before the final transaction summary and before the
transactionIDis executed to MoneyGram on the Commit API.- Pre-disclosure: It is regulatory requirement to show pre-disclosure on every transfer, in every country and for every service option. Learn More
Video Tutorial
Code Examples
const axios = require('axios');
const { v4: uuidv4 } = require('uuid');
const createTransaction = async () => {
// Step 1: Read configuration values with upmost security
const token = "your_access_token_from_oauth_response"
// For production - api.moneygram.com & For test - sandboxapi.moneygram.com
const host = "sandboxapi.moneygram.com";
const url = 'https://' + host + '/transfer/v1/transactions';
// Step 2: Create the POST request headers & body
const headers = {
'Content-Type': 'application/json',
'X-MG-ClientRequestId': uuidv4(), // New UUID for each request tracing
'Authorization': 'Bearer ' + token,
};
const request = {
agentPartnerId: "your_partner_id",
targetAudience: "AGENT_FACING",
userLanguage: "en-US",
destinationCountryCode: "USA",
destinationCountrySubdivisionCode: "US-MN",
serviceOptionCode: "WILL_CALL",
sendAmount: {
currencyCode: "USD",
value: 500
},
receiveCurrencyCode: "USD",
sender: {
name: {
firstName: "firstName",
middleName: "",
lastName: "lastName",
secondLastName: ""
},
address: {
line1: "line 1 of address",
line2: "line 2 of address",
line3: "",
city: "minneapolis",
countrySubdivisionCode: "US-TN",
countryCode: "USA",
postalCode: "53325"
},
mobilePhone: {
number: "6123456789",
countryDialCode: "1"
},
personalDetails: {
genderCode: "MALE",
dateOfBirth: "1980-08-15",
birthCountryCode: "USA",
citizenshipCountryCode: "USA"
},
primaryIdentification: {
typeCode: "PAS",
id: "passport_id_number",
issueCountrySubdivisionCode: "US-MN",
issueCountryCode: "USA"
}
},
receiver: {
name: {
firstName: "firstName",
middleName: "",
lastName: "lastName",
secondLastName: ""
}
}
}
try {
// Step 3: Send the request and obtain the response
axios.post(url, request, { headers })
.then(function (response) {
// Step 4: Parse the success response and process further
// Verify readyForCommit is true, if yes, transaction is ready to commit
console.log(JSON.stringify(response.data, null, 2))
})
.catch(function (error) {
// Step 5: Parse the error response and handle the errors
if (error.response) {
console.log('Response status:', error.response.status);
console.log('Response body:', error.response.data);
} else {
// TODO: handle generic errors
console.error('Error:', error.message);
}
});
} catch (error) {
// TODO: handle exception
console.error('Error:', error.message);
}
};
createTransaction();import requests
import uuid
import json
def create_transaction():
# Step 1: Read configuration values with upmost security
token = "your_access_token_from_oauth_response"
# For production - api.moneygram.com & For test - sandboxapi.moneygram.com
host = "sandboxapi.moneygram.com";
url = 'https://' + host + '/transfers/v1/transactions';
# Step 2: Create the POST request headers & body
headers = {
'Content-Type': 'application/json',
'X-MG-ClientRequestId': str(uuid.uuid4()), # New UUID for each request tracing
'Authorization': 'Bearer ' + token,
}
request = {
'agentPartnerId': 'your_partner_id',
'targetAudience': 'AGENT_FACING',
'userLanguage': 'en-US',
'destinationCountryCode': 'USA',
'destinationCountrySubdivisionCode': 'US-MN',
'serviceOptionCode': 'WILL_CALL',
'sendAmount': {
'currencyCode': 'USD',
'value': 500
},
'receiveCurrencyCode': 'USD',
'sender': {
'name': {
'firstName': 'firstName',
'middleName': '',
'lastName': 'lastName',
'secondLastName': ''
},
'address': {
'line1': 'line 1 of address',
'line2': 'line 2 of address',
'line3': '',
'city': 'minneapolis',
'countrySubdivisionCode': 'US-TN',
'countryCode': 'USA',
'postalCode': '53325'
},
'mobilePhone': {
'number': '6123456789',
'countryDialCode': '1'
},
'personalDetails': {
'genderCode': 'MALE',
'dateOfBirth': '1980-08-15',
'birthCountryCode': 'USA',
'citizenshipCountryCode': 'USA'
},
'primaryIdentification': {
'typeCode': 'PAS',
'id': 'passport_id_number',
'issueCountrySubdivisionCode': 'US-MN',
'issueCountryCode': 'USA'
}
},
'receiver': {
'name': {
'firstName': 'firstName',
'middleName': '',
'lastName': 'lastName',
'secondLastName': ''
}
}
}
try:
# Step 3: Send the request and obtain the response
response = requests.post(url, json=request, headers=headers)
# Step 4: Parse the success response and process further
if response.status_code == 200:
parsed_response = json.dumps(json.loads(response.text), indent=2)
print(parsed_response)
else:
# Step 5: Parse the error response and handle the errors
print("Request failed with status code:", response.status_code)
print(json.dumps(json.loads(response.text), indent=2))
except requests.exceptions.RequestException as e:
# Print any error that occurred during the request
# TODO: handle exception
print("An error occurred:", e)
create_transaction()package transfers;
import javax.json.Json;
import javax.json.JsonObject;
import javax.json.JsonObjectBuilder;
import javax.json.JsonWriter;
import java.io.StringWriter;
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.util.UUID;
public class CreateTransaction {
public static void main(String[] args) {
// Step 1: Read configuration values with upmost security
String token = "your_access_token_from_oauth_response";
// For production - api.moneygram.com & For test - sandboxapi.moneygram.com
String host = "sandboxapi.moneygram.com";
String tokenEndpoint = "https://" + host + "/transfer/v1/transactions";
// Step 2: Create the POST request headers & body
// Create a JSON object
JsonObjectBuilder sendAmountBuilder = Json.createObjectBuilder()
.add("currencyCode", "USD")
.add("value", 500);
JsonObjectBuilder senderBuilder = Json.createObjectBuilder()
.add("name", Json.createObjectBuilder().add("firstName", "firstName").add("lastName", "lastName"))
.add("address", Json.createObjectBuilder().add("line1", "line1 of address").add("city", "minneapolis")
.add("countryCode", "USA").add("countrySubdivisionCode", "US-MN").add("postalCode", "55335"))
.add("mobilePhone", Json.createObjectBuilder().add("number", "6123456789").add("countryDialCode", "1"))
.add("personalDetails", Json.createObjectBuilder().add("dateOfBirth", "1980-01-15").add("birthCountryCode", "USA"))
.add("primaryIdentification", Json.createObjectBuilder().add("typeCode", "PAS").add("id", "passport_id_number").add("issueCountryCode", "USA"));
JsonObjectBuilder receiverBuilder = Json.createObjectBuilder()
.add("name", Json.createObjectBuilder().add("firstName", "firstName").add("lastName", "lastName"));
JsonObjectBuilder requestBuilder = Json.createObjectBuilder()
.add("agentPartnerId", "your_partner_id")
.add("targetAudience", "AGENT_FACING")
.add("userLanguage", "en-US")
.add("destinationCountryCode", "USA")
.add("destinationCountrySubdivisionCode", "US-MN")
.add("serviceOptionCode", "WILL_CALL")
.add("sendAmount", sendAmountBuilder)
.add("receiveCurrencyCode", "USD")
.add("sender", senderBuilder)
.add("receiver", receiverBuilder);
JsonObject jsonObject = requestBuilder.build();
// Create a StringWriter to write the JSON string
StringWriter stringWriter = new StringWriter();
try (JsonWriter jsonWriter = Json.createWriter(stringWriter)) {
jsonWriter.writeObject(jsonObject);
}
// Get the JSON string from the StringWriter
String jsonString = stringWriter.toString();
HttpClient httpClient = HttpClient.newHttpClient();
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create(tokenEndpoint))
.POST(HttpRequest.BodyPublishers.ofString(jsonString))
.setHeader("Authorization", "Bearer " + token)
.setHeader("X-MG-ClientRequestId", String.valueOf(UUID.randomUUID()))
.build();
try {
// Step 3: Send the request and obtain the response
HttpResponse<String> response = httpClient.send(request, HttpResponse.BodyHandlers.ofString());
// Retrieve the status code and body from the response
int statusCode = response.statusCode();
// Step 4: Parse the success response and process further
if (statusCode == 200) {
String responseBody = response.body();
System.out.println(responseBody);
} else {
// Step 5: Parse the error response and handle the errors
String responseBody = response.body();
System.out.println(responseBody);
}
} catch (Exception e) {
e.printStackTrace();
// TODO: handle exception
}
}
}Support APIs
To make your development easier, MoneyGram has provided a Reference Data APIs Module that can be queried to provide a list of supported fields, values and associated meta-data to use in your integration.
| Name | HTTP Method | Endpoints | Description |
|---|---|---|---|
| Retrieve Account Deposit Fields | GET | /reference-data/v1/account-deposit | Retrieves required fields for account deposit delivery option |
| Retrieve Countries | GET | /reference-data/v1/Country | Retrieves supported values and metadata for countries |
| Retrieve Countries ISO3 | GET | /reference-data/v1 /countries/{iso3Code} | Retrieves supported values and metadata for countries by ISO 3 Code |
| Retrieve Currencies | GET | /reference-data/v1/currencies | Retrieves supported values and metadata for currencies |
| Retrieve Enumerations | GET | /reference-data/v1/enumerations | Retrieves enumerated values for fields |
| Retrieve Identification Documents | GET | /reference-data/v1/identification-Documents | Retrieves required fields for identification documents |
| Retrieve Service Options | GET | /reference-data/v1/payout-options | Retrieves supported values and metadata for Service Options |
API Structure
Header Parameters
Field | Type | Required | Description |
|---|---|---|---|
| String | Required | Client Request Id that can be passed by the client application. Client request Id must be unique within a single session for unique requests. This attribute can be used for ensuring idempotent request processing for some APIs. MoneyGram recommends using a UUID for the value of this field. |
| String | Optional | IP Address of the system initiating the sessio |
Request Body Parameters
| Body Parameter | Description |
|---|---|
| TransactBySendAmountRequest | Transact by send amount |
| TransactByReceiveAmountRequest | Transact by receive amount |
Request Body Fields
Field | Type | Required | Description |
|---|---|---|---|
| String | Required | Tailors MoneyGram’s error messages and field metadata to an in-store, digital or crypto consumer. (Enumerated value) |
| String | Required | Unique identifier for the agent or partner |
| String | Optional | Point of sale identifier of the client performing the API Call |
| String | Required | Operator name or ID of the user performing the transaction. Name or ID must be populated from the agent/partner system and cannot be edited by the user. |
| String | Optional | Language used by the user/operator |
| String | Required | Transaction Destination Country (ISO alpha-3 code) |
| String | Conditionally Required | Destination state/province is conditionally required when transacting to the United States or Canada. |
| String | Required | Unique category code to identify the transaction method |
| String | Required | Unique identifier of the individual banking, wallet, or card provider for the service option. |
| Number | Required | Transaction amount and currency excluding fees and exchange rate. |
| String | Required | The |
| String | Required | Receive currency code for the destination country transactBySendAmount Request (ISO alpha-3 code) |
| Number | Required | Transaction receive amount excluding fees and exchange rate for a transactByReceiveAmountRequest Transaction Currency (ISO alpha-3 code) |
| String | Required | The |
| String | Required | Transaction send currency code for a transactBySendAmountRequest |
| [Array] String | Optional | Unique code to apply a promotional discount |
| String | Optional | Unique code to apply Loyalty accrual/redemption (MoneyGram Plus Number) |
| Boolean | Optional | Request MoneyGram to place the transaction on hold |
| Boolean | Optional | Flag to indicate transaction is to be funded in store within a 24hour period |
| String | Optional | Unique store identifier where transaction will be funded |
| String | Optional | Funding method, based on enumerations |
| String | Optional | Name of the payment provider |
| String | Optional | Providers unique network identifier code (Enumerated values) |
| String | Optional | Account number of payment source |
| String | Optional | MoneyGram's unique identifier for the consumer account |
| Dynamic | Optional | Dynamic field key/values |
| String | Required | First Name |
| String | Optional | Middle Name (if applicable) |
| String | Required | Last Name |
| String | Optional | Second Last Name |
| String | Required | Residence address line 1 |
| String | Optional | Residence address line 2 (if applicable) |
| String | Optional | Residence address line 3 (if applicable) |
| String | Required | City of residence |
| String | Optional | State/province of residence |
| String | Required | Country of residence (ISO Alpha-3 Code) |
| String | Optional | Postal/Zip code of residence |
| String | Required | Phone number |
| String | Required | Country dial code |
| String | Optional | Email address |
| Boolean | Optional | Enroll in MoneyGram's Plus Rewards program |
| String | Optional | Consumer notification preference types. Which types of notifications would the consumer like to receive.
|
| String | Optional | Delivery method of notification |
| Boolean | Optional | Flag to declare consumer opts-in to notification type and method |
| String | Optional | Language (ISO Alpha-3 code) |
| String | Optional | Gender (Enumerated Values) |
| String | Required | Date of birth (YYYY-MM-DD) |
| String | Optional | City of birth |
| String | Optional | Country of birth (ISO alpha-3 code) |
| String | Optional | Citizenship Country (ISO alpha-3 code) |
| String | Optional | Occupation/Employment (Enumerated Values) |
| Boolean | Optional | Flag to declare a Politically Exposed Person (PEP) |
| String | Optional | Country of citizenship (ISO alpha-3 code) |
| String | Required | Type of identification document (Enumerated Values) |
| String | Required | Identification document number |
| String | Optional | Issuing state/province of identification document. |
| String | Required | Issuing country of identification document. (ISO alpha-3 code) |
| String | Optional | Expiration year of identification document (YYYY) |
| String | Optional | Expiration month of identification document (MM) |
| String | Optional | Expiration month of identification document (DD) |
| String | Optional | Issuing authority of identification document. (Enumerated values) |
| String | Optional | Issuing city of identification document |
| String | Optional | Issuing year of identification document (YYYY) |
| String | Optional | Issuing month of identification document (MM) |
| String | Optional | Issuing day of identification document (DD) |
| String | Optional | Type of identification document (Enumerated Values) |
| String | Optional | Identification document number |
| String | Optional | Issuing state/province of identification document. |
| String | Optional | Issuing country of identification document. (ISO alpha-3 code) |
| String | Optional | Expiration year of identification document (YYYY) |
| String | Optional | Expiration month of identification document (MM) |
| String | Optional | Expiration month of identification document (DD) |
| String | Optional | Issuing authority of identification document (Enumerated values) |
| String | Optional | Issuing city of identification document |
| String | Optional | Issuing year of identification document (YYYY) |
| String | Optional | Issuing month of identification document (MM) |
| String | Optional | Issuing day of identification document (DD) |
| String | Optional | Type of Additional address (Enumerated Values) |
| String | Optional | Residence address line 1 |
| String | Optional | Residence address line 2 (if applicable) |
| String | Optional | Residence address line 3 (if applicable) |
| String | Required | City of residence |
| String | Optional | State/province of residence. |
| String | Required | Country of residence. (ISO alpha-3 code) |
| String | Optional | Postal code/ZIP of residence |
| String | Optional | Type of family name
|
| String | Optional | First Name |
| String | Optional | Middle Name (if applicable) |
| String | Optional | Last Name |
| String | Optional | Second Last Name (if applicable) |
| String | Optional | Consumer's unique MoneyGram profile identifier |
| String | Optional | Dynamic field key/values |
| String | Required | First Name |
| String | Optional | Middle Name (if applicable) |
| String | Required | Last Name |
| String | Optional | Second Last Name (if applicable) |
| String | Optional | Residence address line 1 |
| String | Optional | Residence address line 2 (if applicable) |
| String | Optional | Residence address line 3 (if applicable) |
| String | Optional | City of residence |
| String | Optional | State/province of residence. |
| String | Optional | Country of residence. (ISO alpha-3 code) |
| String | Optional | Postal code/ZIP of residence |
| String | Optional | Phone number |
| String | Optional | Country dial code |
| Boolean | Optional | Flag to indicate the receiver and sender are the same person |
| String | Optional | Explanation or reason for transferring funds (Enumerated Values) |
| String | Optional | Declaration of where the transaction funds were sourced. |
| String | Optional | Proof of where the transaction funds were sourced (Enumerated Values) |
| String | Optional | Explanation for using MoneyGram service (Enumerated Values) |
| String | Optional | Declaration of consumer's relationship to the sender (Enumerated Values) |
| String | Optional | Primary receipt language of the transacting partner |
| String | Optional | Secondary receipt language of the transacting partner |
| String | Optional | Receipt image string of the transacting partner |
| String | Optional | Partner’s unique session identifier |
| Dynamic | Optional | Dynamic field key/values |
Response Fields
Field | Type | Required/ | Description |
|---|---|---|---|
| Boolean | Optional | Indicates whether the transaction can proceed to commit |
| String | Optional | Unique code to apply Loyalty accrual/redemption (MoneyGram Plus Number) |
| String | Optional | Unique identifier for the transaction resource |
| String | Optional | Consumer facing name to identify the transaction method |
| String | Required | Consumer facing name to identify the transaction method |
| String | Optional | Unique code to identify the individual transaction method |
| String | Optional | Unique name to identify the individual transaction method |
| Number | Required | Transaction amount and currency excluding fees and exchange rate. Transaction Currency (ISO alpha-3 code) |
| String | Required | The |
| Number | Required | Fee Amount and Fee Currency applied to transaction (Fee currencyCode uses ISO alpha-3 code) |
| String | Required | The |
| Number | Conditionally Required | Tax Amount and Tax Currency applied to the Transaction by the the origin country (Tax currency Code uses ISO alpha-3 code) |
| String | Conditionally Required | The |
| String | Conditionally Required | Code to indicate if the fee is to be collected by MoneyGram or the partner |
| String | Conditionally Required | Consumer facing name to identify the charge type |
| Number | Conditionally Required | Additional fee's amount |
| String | Conditionally Required | The |
| String | Optional | Transaction discount amount applied and currency type excluding fees and exchange rate. Transaction discount currencyCode (ISO alpha-3 code) |
| String | Optional | Additional Details about the applied promotion to the transaction. currencyCode (ISO alpha-3 code) |
| Number | Required | Transaction Total Amount and Transaction Total Currency including fees, taxes and discount. (Total currencyCode uses ISO alpha-3 code) |
| String | Required | The |
| Number | Required | Transaction Received Amount and Transaction Receive currency. (Receive amount currencyCode uses ISO alpha-3 code) |
| String | Required | The |
| Number | Optional | Received Fee and Receive Currency applied to the transaction by the destination country. (Receve fee currencyCode uses ISO alpha-3 code) |
| String | Optional | The |
| Number | Optional | Tax Amount and Tax Currency applied to the Transaction by the the origin country. (Receive taxes currencyCode uses ISO alpha-3 code) |
| String | Optional | The |
| String | Optional | Code to indicate if the fee is to be collected by MoneyGram or the partner |
| String | Optional | Consumer facing name to identify the charge type |
| String | Optional | Additional fee's amount |
| String | Optional | The |
| Number | Required | Receive Amount Total and Receive Transaction Currency to be picked-up/deposited in destination country including fees, taxes and discount (Receive total currencyCode uses ISO alpha-3 code) |
| String | Required | The |
| Number | Required | Fx Rate applied to transaction |
| Boolean | Optional | Indicates whether the Fx is “estimated” and amount, taxes and total cannot be guaranteed. The word “estimated” must appear before receiveAmount.amount, receiveAmount.fees, receiveAmount.taxes and receiveAmount.total only when true |
| String | Optional | Unique Identifier for Target Account Resource |
| Dynamic | Optional | Dynamic field key/values |
Updated 29 days ago

Download code examples