Create Account Transfer

post

https://api-{corename}.{env}.gpsrv.com/intserv/4.0/createAccountTransfer

Use the Create Account Transfer endpoint to move funds between accounts in the same program. You can combine a fee with the payment or adjustment, depending on what transaction types you have set up with Galileo. The accounts can belong to the same customer or different customers. If the accounts are in different programs, verify that the program parameters permit transferring funds between the programs.

Pass the sending account in the accountNo parameter and the receiving account in the transferToAccountNo parameter. The receiving account should be in status: N (active) and the active flag set to Y.

To permit this endpoint to drive the sending account negative, set the ALWNB parameter on the sending product.

Consult the Creating an Internal Transfer guide for instructions on using this endpoint.

Status codes

See Global Response Statuses for status codes that are common across endpoints.

The table below lists status codes that apply to this specific endpoint.

Status code	Description
445-01	`The transfer-to account could not be found`. Retry with a valid account number in `transferToAccountNo` or inform the customer that the receiving account does not exist.
445-02	`Invalid transfer-to account`. Verify that the receiving account is `status: N`, or inform the customer that the receiving account is ineligible to receive funds.
445-03	`The transfer-to account product is not authorized`. Inform the customer that the receiving account is not eligible to receive funds.
445-04	`Sender velocity check failure`. Moving funds out of this account violates its velocity limits. Inform the customer that they cannot make this transfer.
445-05	`Recipient velocity check failure`. Moving funds into this account violates its velocity limits. Inform the customer that they cannot make this transfer.
445-06	`Sender insufficient balance`. The value in `amount` is higher than the sending account's available funds. Inform the customer that they do not have sufficient funds to make this transfer.
445-07	`Invalid/unconfigured cross program transfer`. The sending and receiving accounts have different program_ids, and settings do not permit transfers between these programs. Verify that your program settings permit transfers between the two programs, or inform the customer that they cannot transfer funds between those two accounts.
445-08	`Previous attempt found in process. Did not process current request.` Do not retry.

Form Data

apiLogin

string

required

Web service username, as provided by Galileo.
Pattern: Max 50 characters
Example: "AbC123-9999"

apiTransKey

string

required

Web service password, as provided by Galileo.
Pattern: Max 15 characters
Example: "4sb62fh6w4h7w34g"

providerId

int32

required

Galileo-issued provider identifier.
Pattern: Max 10 digits
Example: 9999

transactionId

string

required

1 to 60

A unique provider-generated ID to identify this API call. A UUID is preferred.
Pattern: 60 characters or less
Example: "9845dk-39fdk3fj3-4483483478"

accountNo

string

required

The PRN or PAN of the sending account.
Pattern: PAN or PRN
Example: "074103447228"

amount

float

required

≥ 0.01

Currency amount as a whole or decimal amount.
Pattern: Positive integer or decimal number
Example: 100.00, 100, or 100.73

transferToAccountNo

string

required

The PAN or PRN of the receiving account.
Pattern: PAN or PRN
Example: "074103447228"

message

string | null

A message for the transfer recipient. The C2DSC provider parameter must be set to 1 to populate this parameter. If you do not populate this parameter, it defaults to the value in the BMNAM product parameter. Galileo truncates this field to 80 characters.
Pattern: Max 2000 Windows-1252 characters
Example: "Thanks again for lunch!"

senderMessage

string | null

A message for the transfer sender. The C2DSC provider parameter must be set to populate this parameter. If you do not populate this parameter, it defaults to the value in message.
Pattern: Max 80 Windows-1252 characters
Example: "Thanks again for lunch!"

type

string | null

Transaction type for the transfer. Use the values provided by Galileo for your program.
Pattern: Max 3 alphanumeric characters, case-sensitive
Example: "MRM"

Headers

response-content-type

string

enum

Defaults to json

Use this header instead of the standard accept header to specify the response format.

Allowed:

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Response

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

application/xml