POST/transactions/{userId}/cross-border/preview

Preview Cross Border Payment

Previews a cross-border payment before execution. Returns exchange rate, fees, and destination amount breakdown.

Path variables

FieldTypeRequiredPossible valuesDescription
userIdstringRequired

Unique user ID initiating the cross-border payment.

Headers

FieldTypeRequiredPossible valuesDescription
session-tokenstringRequired

SessionToken obtained from the Create GMA Session endpoint. All secured endpoints require this header.

Request body

FieldTypeRequiredPossible valuesDescription
InstrumentIdstringRequired

Cross-border payment instrument ID.

DestinationAmountstringRequired

Amount in destination currency.

DestinationCurrencystringRequiredGBP | EUR | SGD | AED | ARS | BRL | CAD | JPY | MXN | HKD | ZAR

Target currency for the cross-border payment.

PurposestringRequiredRefer to the Payment Purpose endpoint to get the list of possible values.

Payment purpose code.

CryptoBuySellActivitystringRequiredYes | No

Indicates crypto activity.

DescriptionstringOptional

Payment description.

DocumentReferenceNumberstringOptional

Reference number for supporting document.

SupportingDocumentstringOptional

File ID from the File Upload endpoint. Required when the source amount exceeds the configured threshold for the user's group. The threshold value can be retrieved from the Config Data endpoint.

Additional_InfoobjectOptional{ Originator_Identity_Type: PASSPORT | NATIONAL_ID | DRIVING_LICENSE , Originator_Identity_Number, Source_Of_Funds: CASH | BUSINESS | GIFT | LOTTERY | SAVINGS | OTHER }

Additional compliance fields: Originator_Identity_Type, Originator_Identity_Number, Source_Of_Funds.

Example request

{
  "InstrumentId": "{{instrumentId}}",
  "DestinationAmount": "50.00",
  "DestinationCurrency": "GBP",
  "Description": "GBP payment test",
  "Purpose": "Asset_Purchase",
  "CryptoBuySellActivity": "No",
  "DocumentReferenceNumber": "1234",
  "SupportingDocument": "-3928373292172922988"
}

Response

FieldTypePossible valuesDescription
ResponseCodeinteger200 | 201 | 204 | 301 | 400 | 401 | 403 | 404 | 410 | 422 | 500 | 503

API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized).

ResponseMessagestringSuccess | Created | NoContent | BadRequest | Unauthorized | Forbidden | NotFound | Gone | UnprocessableContent | ServerError | ResourceMoved | ServiceUnAvailable | UnProcessableEntity

Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome.

ResponseDataobjectPlease refer to below example for response body

Cross-border payment preview with exchange rate, fees, and source/destination amounts.

Example response

{
  "ResponseCode": 200,
  "ResponseMessage": "Success",
  "ResponseData": {
    "BeneficiaryPaymentInstrumentID": "-9125527262158475302",
    "From": "John Doe",
    "To": "UK Faster Payments Account",
    "DestinationAmount": "50",
    "DestinationCurrency": "GBP",
    "FXRate": "1.349851",
    "SourceAmount": "67.49255",
    "FeeInUSD": "35",
    "TotalAmountInUSD": "102.49255",
    "QuoteId": "54e0f55f-9f9c-49d9-9f87-ace7feb95617",
    "Purpose": "Asset_Purchase",
    "Description": "SEPA payment test"
  }
}

Use Perform Cross Border Payment to execute after previewing.

Requires `session-token: {SessionToken}` from Create GMA Session. Use the same client IP as authentication.

Search guide books, endpoints, paths, or parameters

↑↓navigateopenEscclose