Testing Direct Debit Payments

In your demo environment, create a test payment with the following data:

1. Payer information (Magic Values)

Use any placeholder data you'd like for the required payer information like first name, last name etc.

For the payer's middle name use one of the magic values depending on the scenario you want to test:

Successful Payment - realistic disbursement

This scenario simulates a successful payment that moves into delivered after 24 hours. This is a realistic scenario since payments get disbursed every 24 hours. If you create multiple test payments like this, you create a realistic disbursement file that contains multiple payments.

Payer's Middle Name	Payment Flow	Callbacks you will receive
SANDBOX_TO_GUARANTEED_STATUS	Initiated > Processed > Guaranteed > (after 24 hours) Delivered	Initiated Processed Guaranteed After 24 hours: Delivered

Successful Payment - disbursed immediately

This magic value moves a payment into delivered immediately.

 

Payer's Middle Name	Payment Flow	Callbacks you will receive
SANDBOX_TO_DELIVERED_STATUS	Initiated > Processed > Guaranteed > Delivered	Initiated Processed Guaranteed Delivered

Unsuccessful Payment - cancelled payment

This can happen for any payment method when then payment gets cancelled by you, the payer, or by Flywire.

 

Payer's Middle Name	Payment Flow	Callbacks you will receive
SANDBOX_TO_CANCEL_STATUS	Initiated > Cancelled	Initiated Cancelled

Successful Payment - with simulated successful verification

This can happen for any payment method if a manual review (for example document collection or quality checks) is necessary.

This magic value simulates a payment that fails automated checks and gets routed to manual review which ends up being successful.

 

Payer's Middle Name	Payment Flow	Callbacks you will receive
SANDBOX_TO_VERIFICATION	Initiated > Processed > after 2 hoursGuaranteed	Initiated Processed After 2 hours: Guaranteed

Unsuccessful Payment - with simulated failed verification

This can happen for any payment method if document collection or quality checks fail and cannot be manually corrected by contacting the payer.

The magic value simulates a payment that fails automated checks and gets routed to manual review and fails the check.

 

Payer's Middle Name	Payment Flow	Callbacks you will receive
SANDBOX_TO_VERIFICATION_FAILED	Initiated > Processed > after 2 hours Cancelled	Initiated Processed After 2 hours: Cancelled

This can happen for payments made via any payment method.

After Flywire receives the funds, the transaction is flagged as suspicious and is placed on hold. The payment is manually checked to determine legitimacy. There can be two outcomes:

• If the alert is deemed to be a false positive, Flywire will deliver the funds.

• If the risk profile of the payment is deemed higher than Flywire thresholds allow (payment is deemed to be suspicious and/or the alert cannot be deemed a false-positive), the payment will be cancelled. Flywire will notify you and return the funds to the payer.

  Initiated > Processed > Guaranteed > Cancelled

2. Payment option

Choose a direct debit payment option. Enter the following demo bank account data:

BACS

Sort Code	60 00 01
Account Number	00000019

SEPA

EEA Country

Country	Spain
IBAN	ES7921000813610123456789

Non-EEA Country

Country	United Kingdom
IBAN	GB98MIDL07009312345678
BIC	BOFIIE2D

3. Check the results

You will receive callbacks according to the scenario you chose (see Payment Status Notifications for details).